Date: November 4th
Sendant: Beman Dawes
Topic: C Committee Actions
The C Committee Met Last Week. Actions Which May Be of Interest To Boosters:
C Standards Committee held last week. Some information Booster it should be of interest: * The initial version of the Library Technical Report (TR) working paper has been accepted; it will be refined over the next year to become the final TR The plan is to finish the technical work. On The Tr at the
Redmond
Meeting, One Year from Now.
The initial library Technical Report Working Paper has been accepted by the Standards Committee; in the next year, these reports will be further accurate, and become the final TR. The plan is to complete TR-related technical work before the Redmond meeting next year. * A number of mostly minor changes and fixes to the TR were voted in, based on early implementation experience. Library vendors seem to be implementing the TR with gusto, and one or two are already shipping some of the smaller components.
Most of the major changes and finishing of TR are voted by early realization experience. Library's authors look like to complete TR has a strong interest, and one of them has submitted smaller components. * The Iterator Facade and AdapTor, Iterator Concepts, And Fixed Size Array Wrapper Proposals Were Accepted for the Library Tr. All Are Based On Boost Libraries.
Iterator Facade and Adaptor, Iterator Concepts, and Pixabay Packets have been accepted by the Library TR. These proposals are based on BOOST. * The Library TR is now closed;. No proposals for new components will be accepted The Library Working Group (LWG) will continue to accept defect reports from committee members until the TR is finished (The LWG did not discuss what would happen if. A Non-CommitTee Member Submitted A Defect Report on The Tr Working Paper, But I can't Image IT Would Be ignored.) Library TR is now closed, not accepting new component proposals. The Library Working Group (LWG) will receive an error report from the Standard Commission until the TR work is over. (Although the Library Working Group has not discussed what happens if they receive an error report submitted by a non-standard member member, I think the report should not be ignored)
* The LWG will now begin to accept proposals for changes to the current standard library, for inclusion in C xx. (So called "impure" changes. The TR accepted only "pure" / "bolt-on" additions.) Details NOT YET WORKED OUT, BUT AS Usual Proposals Will Require A Fully-Worded Proposal In The Form of An Official CommTtee Document. The library work team now accepts a modification proposal for the current C XX standard (that is, "Impure" form. TR only accepts proposals in the "pure / bolt-on" form). Although the details are not fully determined, as usual, this proposal requires a formal official format file. * The C (yes, C, not C ) committee decided the previous week to include the Special Functions from the C Library TR as a C library. The intent is to maintain as close to 100% compatibility between the two Special Function libraries as is Possible. CERTAIN Minor Changes Were Made To The Tr Library To Facilitate Compatibility.c Standards Committee (note that C ) determines that special functions in C Library TR are part of a standard C library last week. The initial imagine is that the function between the two standards can reach 100% compatibility. It can therefore be determined that the TR Library will make a little change in compatibility.
* Both the C and C committees are beginning tightly coordinated work on new TR's dealing with "the integration of IEEE-754R decimal floating-point arithmetic" into the two languages. Note that IEEE-754R includes fixed-point and integer decimal point arithmetic as A Subset of floating-point.
The C and C Standards Committee are closely working with the "Ten Element Floating Point System" in the IEEE-754R standard in these two languages. Note that the IEEE-754R standard contains a subset of fixed-point decimal and decimal integer systems as a floating point system.
Translator Note: You can see the IEE-754R standard:
Http://grouper.iee.org/groups/754/meeting-minutes/03-05-29.html
* The ECMA TG5 committee work on C / CLI language bindings is moving forward on a fast track. The leadership and membership of the ECMA committee is dominated by long-term C committee members, so hopefully the two committee's work will be well coordinated.'Re The ECMA TG5 Standards Committee for Binding C and CLI works is very fast. Most of the members of the ECMA Standards Committee are members of the long-term C Standards Committee. Therefore, the collaboration between the two committees will be coordinated. * The C committee's Evolution Working Group continues to work on language changes for C xx. That's a large effort that will take some years to mature, but it does seem clear that many concerns of library developers will be addressed.
C Committee's Evolution Working Group (C core language Working Group) is still unremitting efforts to change in the core language of the C XX standard. Although it is a job that needs to develop maturity for many years, it is obvious that many library workers pay attention to the focus of concern they will not let go. * The committee's schedule for Future Meetings Looks Like this:
Future Standard Board Schedule:
date
location
2004-03-21 / 26
Sydney
,
Australia
2004-10-17 / 22
Redmond
,
WA
,
USA
2005-04
Oslo
,
Norway
2005-09
Sydney
,
Ns
,
Canada
As Usual, Boost Developers May Attend As Outside "Technical Experts". See
http://www.boost.org/more/cpp_committee_meetings.html Contact Me Directly if You NEED More Information.
--Beman
As usual, BOOST developers can participate in the meeting as "technical experts".
Http://www.boost.org/more/cpp_committee has detailed information at http:/cpp_committee_meetings.html. If you need more detailed information, please contact me directly.
Sendant: David B. Held
SO EIW I UNDERSTAND CORRECTLY
If my understanding is correct, the Standard Commission is completed in C 0x and will not accept the new library proposal before the next TR starts. Do we discuss things after 5 years?
Sendant: Mat Marcus
The TR is essentially a set of library proposals that are implementable against C 98/03. The TR is now closed. But we are also working hard at extending C . The result of this effort will become C 200x (2007/8?). In C '0x There Will Be Core Language Extensions (Maybe, Concepts, Template Aliates, Variadic Templates, etc. "In Addition to Library Enhancements.tr is actually a proposal for some implementable libraries for C 98/03. Now, although TR has no longer receive new proposals, we are still working hard to expand C . The results of these efforts will be reflected in C 200x (2007/8?). In C 0x, there will be some core language extensions in addition to the reinforcement of the library (for example, Concepts, Template Aliases, Variadic Templates, etc.
Sendant: Beman Dawes
Here is another way to think about it: the LWG and committee is committed to a continuing process of introducing new standard library components Like other software, the new library components get batched up into releases..
Another way to understand this problem: the responsibility of the Working Group (LWG) and the Standards Committee is constantly adding some new components into the standard library - like other software, the new library components will be in the new The version is constantly being added. .
After a year of testing and refining, the first release of the Library TR has been determined. And will be officially released after one year. Other Library Release 40. Their release dates haven't been set yet.
The issuance of other libraries is also in progress. They have not been determined yet.
Sendant: Beman Dawes
AT
11:38 AM
11/6/2003
, Edward Diener wrote:> Why could not proposals for TR2 be made and accepted while TR1 is being tested That's what is happening Except the current plan is not to have a second batch of additions named TR2, but rather feed the second batch into?. The C 0x Standard Directly.
These are what is happening. Unless the present plan is not prepared for a new branch of TR2, the new branch directly into the C 0x standard. But n't change to a constant stream of standard library enhancements. But these things will change. The unchanging is the library work team will continue to work hard for the expansion of the library.
The schedule depends to a considerable extent on how many people are willing to do the work. The LWG current attracts about 20 people to each meeting, with perhaps 15 people doing the bulk of the year-in year-out work. Because the numbers are Small, Each Additional Volunteer Has A Measurable Impact.
This plan depends on how many people are willing to work for this goal. Now every meeting, there will be approximately 20 people at the banking team, with approximately 15 people work a lot of work per year. Because our number is too little, any new volunteers will have a significant impact.
