Please note that the main trust of my presentation was
(1) no major changes to the language
(2) major extensions to the standard library
Clearly we can/will get some major discussions/fights over the definition of "major" in (1).
My examples of possible minor extensions
(compatible changes) included:
- allow list<vector<int>> (without a space between the >>s
- allow template typedefs
- explitly acknowledge that GC is a valid optional implemenation technique
- make lookup for functions and function objects identical
Most such changes will be compatible and technical.
I'm posting the slides from my talk on my FAQ.
Please note that the purpose of talking about the future now is to have sufficient time for a serious and constructive debate before the standard comes up for revision - not to create a rush of changes for tomorrow. Also note that these are my ideas, not (yet:-) committee policy.
Slashdot Mirror
Consider ACE: http://siesta.cs.wustl.edu/~schmidt/ACE.html
It's open source, more portable than just about anything else, and used in industry.
(1) no major changes to the language
(2) major extensions to the standard library
Clearly we can/will get some major discussions/fights over the definition of "major" in (1). My examples of possible minor extensions
(compatible changes) included: - allow list<vector<int>> (without a space between the >>s
- allow template typedefs
- explitly acknowledge that GC is a valid optional implemenation technique
- make lookup for functions and function objects identical
Most such changes will be compatible and technical. I'm posting the slides from my talk on my FAQ.
Please note that the purpose of talking about the future now is to have sufficient time for a serious and constructive debate before the standard comes up for revision - not to create a rush of changes for tomorrow. Also note that these are my ideas, not (yet:-) committee policy.