Can anyone summarize what kinds of things we should expect in the
impending C++0x? I've heard part of the boost library will be
included, multimethods may be added, templated typedefs. Anything
else?

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

sb wrote:
> Can anyone summarize what kinds of things we should expect in the
> impending C++0x?

I doubt anybody can. There are some ideas, some discussion but I don't
think that there is much definite stuff yet.

> I've heard part of the boost library will be
> included,

There is TR (technical report) on library extensions which currently
includes some of the Boost stuff but far not everything. Smart pointers,
type traits, random stuff, iterator adaptors, function objects, and
regular expressions is from Boost. Hash maps and mathical special
functions are also there. Whether anything will effectively become part
of C++0x is a completely different issue, however.

> multimethods may be added,

Maybe. Personally, I think this is pretty unlikely but then I may be
wrong.

> templated typedefs.

I think this one will be in, in some form or the other.

> Anything else?

Yes, certainly. There is lots of stuff under discussion. What will get
into the standard is still rather unclear, I think. Here is some stuff
which may make some sense from just the name without reading the
associated paper:
- variadic template arguments
- variadic macros
- extending template parameters eg. by namespaces or cv-qualification
- delegating constructors
- strongly typed enums
- a long long type

Since I'm normally in the library group, I don't know what else is
discussed in the evolution group. In any case, I don't think that there
is anything definite, yet.
--
<mailto:dietmar_kuehl@yahoo.com> <http://www.dietmar-kuehl.de/>
Phaidros eaSE - Easy Software Engineering: <http://www.phaidros.com/>

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

Take a look at the proposals: http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

===================================== MODERATOR'S COMMENT:

In responding please do not post passwords to the newsgroup.


===================================== END OF MODERATOR'S COMMENT
Helium wrote:
> Take a look at the proposals: http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/

    The important documents are password protected.

   Try "C++ Core Language Active Issues"

http://anubis.dkuug.dk/jtc1/sc22/wg21/prot/14882fdis/n1571.html

   What's the password?

    John Nagle
    Animats

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

In article <HJl4c.9289$7z6.7299@newssvr27.news.prodigy.com>, John Nagle
<nagle@animats.com> writes
>===================================== MODERATOR'S COMMENT:
>In responding please do not post passwords to the newsgroup.
>
>
>===================================== END OF MODERATOR'S COMMENT
>Helium wrote:
>> Take a look at the proposals: http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/
>
>   The important documents are password protected.
>  Try "C++ Core Language Active Issues"
>
>http://anubis.dkuug.dk/jtc1/sc22/wg21/prot/14882fdis/n1571.html
>
>  What's the password?

Stronger than the moderator's comment, that document is protected
exactly because it is not a public document and there are several other
documents under the same protection which WG21 only has access to under
the strict understanding that access is limited to authorised national
experts.

If you want access you must persuade your NB that you are a bona fide
expert with need for access for the purposes of your work on a Standard.

--
Francis Glassborow      ACCU
Author of 'You Can Do It!' see http://www.spellen.org/youcandoit
For project ideas and contributions: http://www.spellen.org/youcandoit/projects

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

"John Nagle" <nagle@animats.com> wrote
>
>     The important documents are password protected.
>
>    Try "C++ Core Language Active Issues"
>
> http://anubis.dkuug.dk/jtc1/sc22/wg21/prot/14882fdis/n1571.html
>
>    What's the password?

Don't know. .-)

However, there is also a public version of the document, found here:

http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/cwg_active.html


Bo Persson


---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

   Amusingly, the "C++ Library Active Issues" list is available,
but the "C++ Core Language Active Issues, Version 29" list is password
protected, if reached by the link

   "http://anubis.dkuug.dk/jtc1/sc22/wg21/prot/14882fdis/n1571.html"

on the page

   "http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/2004/".

However, the same document is freely available at

   "http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/cwg_active.html".

Determination of the appropriate level of classification of the
relevant documents is left as an exercise for the reader.

    John Nagle
    Animats

Francis Glassborow wrote:
> In article <HJl4c.9289$7z6.7299@newssvr27.news.prodigy.com>, John Nagle
> <nagle@animats.com> writes
>
>> ===================================== MODERATOR'S COMMENT:
>> In responding please do not post passwords to the newsgroup.
>>
>>
>> ===================================== END OF MODERATOR'S COMMENT
>> Helium wrote:
>>
>>> Take a look at the proposals:
>>> http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/
>>
>>
>>   The important documents are password protected.
>>  Try "C++ Core Language Active Issues"
>>
>> http://anubis.dkuug.dk/jtc1/sc22/wg21/prot/14882fdis/n1571.html
>>
>>  What's the password?
>
>
> Stronger than the moderator's comment, that document is protected
> exactly because it is not a public document and there are several other
> documents under the same protection which WG21 only has access to under
> the strict understanding that access is limited to authorised national
> experts.

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

"Francis Glassborow" <francis@robinton.demon.co.uk> wrote in message
news:hSBxAUEKXfUAFwPs@robinton.demon.co.uk...
> In article <HJl4c.9289$7z6.7299@newssvr27.news.prodigy.com>, John Nagle
> <nagle@animats.com> writes
> >===================================== MODERATOR'S COMMENT:
> >In responding please do not post passwords to the newsgroup.
> >
> >
> >===================================== END OF MODERATOR'S COMMENT
> >Helium wrote:
> >> Take a look at the proposals:
http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/
> >
> >   The important documents are password protected.
> >  Try "C++ Core Language Active Issues"
> >
> >http://anubis.dkuug.dk/jtc1/sc22/wg21/prot/14882fdis/n1571.html
> >
> >  What's the password?
>
> Stronger than the moderator's comment, that document is protected
> exactly because it is not a public document and there are several other
> documents under the same protection which WG21 only has access to under
> the strict understanding that access is limited to authorised national
> experts.
>
> If you want access you must persuade your NB that you are a bona fide
> expert with need for access for the purposes of your work on a Standard.
>

   I understand the need to keep some documents password-protected, but it
would be nice if the website indicated which links are open to the public
and which require passwords.  I always find it annoying when I innocently
click on a link and get a "please enter password" message box.

Joe Gottman

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

John Nagle wrote:

>   Amusingly, the "C++ Library Active Issues" list is available,
> but the "C++ Core Language Active Issues, Version 29" list is password
> protected, if reached by the link
>   "http://anubis.dkuug.dk/jtc1/sc22/wg21/prot/14882fdis/n1571.html"
>
> on the page
>
>   "http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/2004/".
>
> However, the same document is freely available at
>
>   "http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/cwg_active.html".

It's not exactly "the same document."  There's a committee
version and a public version; the committee version has some
additional administrative information beyond what is in the
public version.  For example, we decided not to publicize the
drafting assignments for the various issues, for the same reason
that the membership list is not public: we didn't want to expose
individual members involuntarily to potential lobbying, reprisals
for unpopular decisions, etc.  The technical content of the two
versions is identical.
--
William M. Miller, The MathWorks, Inc.
wmm@world.std.com

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

spam_bait101@yahoo.com (sb) wrote in message news:<221dd125.0403072257.167b8544@posting.google.com>...
> Can anyone summarize what kinds of things we should expect in the
> impending C++0x? I've heard part of the boost library will be
> included, multimethods may be added, templated typedefs. Anything
> else?

You can get an idea by looking at
http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/2004/#pre_sydney. Some
of the papers are for the committee only, and these are password
protected. But most are available to the public.

Remember that all proposals won't be accepted, and those that are
accepted will often be changed in the process. If a proposal has gone
through several revisions then it usually means the author is getting
feedback from the committee and adjusting accordingly.

Since a lot of committee members read this newsgroup, you can give
them your technical views and options on proposals by posting a
comment here. Keeping comments brief increases the likelyhood they
will be read.

--Beman Dawes

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]