はてなブックマーク

P3477R0 There are exactly 8 bits in a byte Published Proposal, 2024-10-15 This version: http://wg21.link/P3477r0 Author: JF Bastien (Woven by Toyota) Audience: EWG, LEWG, SG22 Project: ISO/IEC 14882 Programming Languages — C++, ISO/IEC JTC1/SC22/WG21 Source: github.com/jfbastien/papers/blob/master/source/P3477r0.bs 1. Rationale C has the CHAR_BIT macro which contains the implementation-defined num

Introduction Many implementations provide extensions that allow programmers to attach a block of cleanup code to another block or function such that this cleanup code is executed unconditionally when execution of the block is terminated. These existing extensions don’t have a unified API, some use pseudo-function calls, some compiler specific attributes and yet another a try/finally notion. In a f

This is a response to N1509: Optimizing away infinite loops. My goal is to explain the rationale behind the current wording. The question of whether or not side-effect-free infinite loops have defined semantics impacts primarily compiler back-ends. As we show below, guaranteeing stronger properties for infinite loops, as suggested in N1509, inhibits certain optimizations. Since compiler back-ends

Document number: N1865 Submitter: Martin Sebor Submission Date: September 19, 2014 Subject: scope of a for loop control declaration Summary The scope of a for loop control declaration in C is different from that in C++. In particluar, while in C the declaration establishes its own scope in which the scope of the body of the for statement is nested, in C++ the two are one and the same. The practica

Document number: P0534R3 Date: 2017-10-15 Reply-to: Oliver Kowalke (oliver.kowalke@gmail.com) Authors: Oliver Kowalke (oliver.kowalke@gmail.com), Nat Goodspeed (nat@lindenlab.com) Audience: LEWG call/cc (call-with-current-continuation): A low-level API for stackful context switching Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Native Json & HTML, built-in tutorial, easy meta programming, reflection proposal to C++ Why? C++ is a great programming language, but it falters when we try to use it for cloning and generating code parts. Programmable code generators let you create very complex clones of a given code part (class, enums, templates, statements, etc.) with familiar syntax. The result is extraordinarily expressive,

C - Approved standards 2013-03-05: home | projects | documents | contributing | meetings | contacts ISO/IEC 9899 - Programming languages - C The current standard for Programming Language C (C11) is ISO/IEC 9899:2011, published 2011-12-08. Technical Corrigendum 1 (ISO/IEC 9899:2011/Cor. 1:2012) was published in 2012. Published ISO and IEC standards can be purchased from a member body of ISO or IEC.

Document Number: N3337 Date: 2012-01-16 Revises: N3291 Reply to: Stefanus Du Toit Intel Corporation cxxeditor@gmail.com Working Draft, Standard for Programming Language C++ Note: this is an early draft. It’s known to be incomplet and incorrekt, and it has lots of bad for matting. c ISO/IEC N3337 Contents Contents ii List of Tables x List of Figures xiv 1 General 1 1.1 Scope . . . . . . . . . . . .

N1570 Committee Draft — April 12, 2011 ISO/IEC 9899:201x INTERNATIONAL STANDARD ©ISO/IEC ISO/IEC 9899:201x Programming languages — C ABSTRACT (Cover sheet to be provided by ISO Secretariat.) This International Standard specifies the form and establishes the interpretation of programs expressed in the programming language C. Its purpose is to promote portability, reliability, maintainability, and e

N1548 Committee Draft — December 2, 2010 ISO/IEC 9899:201x INTERNATIONAL STANDARD ©ISO/IEC ISO/IEC 9899:201x Programming languages — C ABSTRACT (Cover sheet to be provided by ISO Secretariat.) This International Standard specifies the form and establishes the interpretation of programs expressed in the programming language C. Its purpose is to promote portability, reliability, maintainability, and

WG14/N1124 Committee Draft — May 6, 2005 ISO/IEC 9899:TC2 Contents Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv 1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2. Normative references . . . . . . . . . . . . . . . . . . . . . . . 2 3. Terms, definitions, and symbols . . . . . . .

N1615 C++ Properties – a Library Solution Page 1 of 14 Document Number: SC22/WG21/N1615=04-0055 Date: 2004-04-09 Author: Lois Goldthwaite Email: Lois@LoisGoldthwaite.com C++ Properties -- a Library Solution N1600 is a summary of the "property" language extension that is proposed for C++/CLI. I can't help feeling that this is an effort to impose an alien idiom on C++. There is too much of "the comp

Background The gets function in the stdio.h section of the C standard has long been a source of programming errors and vulnerabilities. Many compilers issue a warning when it is used. In TC3, WG14 marked this function as obsolete. This paper is intended to give editorial direction to the project editor to completely remove this function from the next revision of the standard. Compiler and library

C - Project status and milestones 2024-08-07: home | projects | documents | contributing | meetings | contacts ISO/IEC 9899 - Revision of the C standard The primary output of WG14 is ISO/IEC 9899, the C Standard. The following is a list of revisions to ISO/IEC 9899 that the committee has produced: RevisionISO publicationSimilar draft

WG14/N1124 Committee Draft — May 6, 2005 ISO/IEC 9899:TC2 Contents Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv 1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2. Normative references . . . . . . . . . . . . . . . . . . . . . . . 2 3. Terms, definitions, and symbols . . . . . . .

C++ - TR 18015 Technical Report on C++ Performance Tuesday, 14-Feb-2006 17:22:41 UTC home | standards | projects | papers | mailings | internals | meetings | contacts ISO/IEC JTC1/SC22/WG21 has produced the Technical Report ISO/IEC 18015:2006 on C++ Performance. The Final draft is available. New examples and references will also be posted here, as they become available. The project editor is Lois

C - Approved standards 2013-03-05: home | projects | documents | contributing | internals | meetings | contacts ISO/IEC 9899 - Programming languages - C The current standard for Programming Language C (C11) is ISO/IEC 9899:2011, published 2011-12-08. Technical Corrigendum 1 (ISO/IEC 9899:2011/Cor. 1:2012) was published in 2012. Published ISO and IEC standards can be purchased from a member body of

2024-02-16: standards | projects | papers | mailings | internals | meetings | contacts News 2024-02-15: The deadline for the 2024-04 mailing is 2024-04-16 16:30 UTC News 2024-02-15: The 2024-02 pre-Tokyo mailing is available (13000 kB tar.gz), individual papers News 2024-01-16: The 2024-01 mailing is available (4000 kB tar.gz), individual papers News 2023-12-22: The C++ Standard Core Issues List (

C++ Standard Core Language Active Issues, Revision 115 This document contains the C++ core language issues on which the Committee (INCITS PL22.16 + WG21) has not yet acted, that is, issues with status "Ready," "Tentatively Ready," "Review," "Drafting," and "Open." (See Issue Status below.) This document is part of a group of related documents that together describe the issues that have been raised

WG14/N1124 Committee Draft — May 6, 2005 ISO/IEC 9899:TC2 Contents Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv 1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2. Normative references . . . . . . . . . . . . . . . . . . . . . . . 2 3. Terms, definitions, and symbols . . . . . . .

1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 These are all of the papers currently available online. If you've written papers that are not available here, and would like to donate them to the collection, or if you have HTML versions of any of these papers get in to