下一个C ++的ISO / ANSI标准 [英] next ISO/ANSI standard for C++
问题描述
您好！
您知道什么时候会批准c ++的新标准吗？什么
将在里面？希望会有一些线程和同步类，
文本和XML解析，新容器和其他新东西。上帝拯救我
来自无聊的编码慢慢的没有指针java !!
ps：编译器厂商通常需要多少时间才能实现
新标准？
ps2：谁知道哪个编译器支持导出关键字？
感谢大家。
Hello!
Do you know when will be the new standard for c++ approved? And WHAT
will be inside? Hope there will be some thread and synchro classes,
text and XML parsing, new containers and other new things. God save me
from coding in boring & slow & no pointers java!!
p.s.: how much time usually needs the compiler vendors to implement
new standards?
p.s.2: anybody knows which compiler supports export keyword?
Thanks to you all.
推荐答案
skoco < SK ******* @ yahoo.com>在消息中写道
news：d7 ************************** @ posting.google.c om ...
"skoco" <sk*******@yahoo.com> wrote in message
news:d7**************************@posting.google.c om...
您好！
您知道什么时候会批准c ++的新标准吗？什么
将在里面？希望会有一些线程和同步类，文本和XML解析，新容器和其他新东西。上帝拯救我
来自无聊的编码慢慢的没有指针java !!
ps：通常需要多长时间编译器厂商实现新标准？
ps2：谁知道哪个编译器支持export关键字？
Hello!
Do you know when will be the new standard for c++ approved? And WHAT
will be inside? Hope there will be some thread and synchro classes,
text and XML parsing, new containers and other new things. God save me
from coding in boring & slow & no pointers java!!
p.s.: how much time usually needs the compiler vendors to implement
new standards?
p.s.2: anybody knows which compiler supports export keyword?
我不知道C ++标准何时会再次被修改。但我真的希望
这次你提到的东西，比如线程，XML解析等等。
现在jdk1.5已经出来并且它具有泛型支持（在模板上）线路），C ++
也应该以标准的方式使用其他东西变得足够丰富。
不知道我们的编译器供应商将花多少时间采用新的增加。
可能像Greg Comeau这样的人可以对此发表评论:-)
现在只有Comeau对出口关键字AFAIK有适当的支持。
-Sharad
I don''t know when C++ standard is going to be revised again. But I really wish
that things you mentioned like threads, XML parsing etc are included this time.
Now that jdk1.5 is out and it has generics support (on template lines), C++
should also get rich enough with other things in a standard way.
No idea how much time our compiler vendors will take to adopt the new additions.
May be people like Greg Comeau can comment on this :-)
Right now only Comeau has proper support for export keyword AFAIK.
-Sharad
*这样讲过skoco< sk ******* @ yahoo.com>：
你好，
* Thus spoke skoco <sk*******@yahoo.com>:
Hallo,
你知道什么时候会批准c ++的新标准吗？
编号我的猜测是我们很快就不会看到它了。 （2006-2009）
什么会在里面？
< http://std.dkuug.dk/jtc1/sc22/wg21/>
ps：编译器供应商通常需要多长时间实施新标准？
Do you know when will be the new standard for c++ approved?
No. My guess is that we won''t be seeing it any time soon. (2006-2009)
And WHAT will be inside?
<http://std.dkuug.dk/jtc1/sc22/wg21/>
p.s.: how much time usually needs the compiler vendors to implement
new standards?
太长了。 ;-)
沃尔夫冈。
-
我记得当我意识到生命的很大一部分时的确切时刻<从那时起，
将用于在我自己的程序中发现错误。
- Maurice Wilkes，1947
Too long. ;-)
Wolfgang.
--
"I can remember the exact instant when I realized that a large part of my life
from then on was going to be spent in finding mistakes in my own programs."
-- Maurice Wilkes, 1947
" Sharad Kala" <无***************** @ yahoo.com>写了
"Sharad Kala" <no*****************@yahoo.com> wrote
skoco < SK ******* @ yahoo.com>写了
"skoco" <sk*******@yahoo.com> wrote
你好！
你知道什么时候会批准c ++的新标准吗？什么
将在里面？希望会有一些线程和同步类，文本和XML解析，新容器和其他新东西。上帝拯救我
来自无聊的编码慢慢的没有指针java !!
ps：通常需要多长时间编译器厂商实现新标准？
ps2：谁知道哪个编译器支持导出关键字？
我不知道不知道C ++标准何时会再次被修改。但我真的希望你提到的东西，比如线程，XML解析等都包括在这个
Hello!
Do you know when will be the new standard for c++ approved? And WHAT
will be inside? Hope there will be some thread and synchro classes,
text and XML parsing, new containers and other new things. God save me
from coding in boring & slow & no pointers java!!
p.s.: how much time usually needs the compiler vendors to implement
new standards?
p.s.2: anybody knows which compiler supports export keyword?
I don''t know when C++ standard is going to be revised again. But I really wish
that things you mentioned like threads, XML parsing etc are included this
时间内。现在jdk1.5已经出来并且它具有泛型支持（在模板行上），C ++
也应该以标准的方式充分利用其他东西。
不知道我们的编译器供应商会花多少时间采用新的
增加。也许像Greg Comeau这样的人可以对此发表评论:-)
现在只有Comeau对出口关键字AFAIK有适当的支持。
time. Now that jdk1.5 is out and it has generics support (on template lines), C++
should also get rich enough with other things in a standard way.
No idea how much time our compiler vendors will take to adopt the new
additions. May be people like Greg Comeau can comment on this :-)
Right now only Comeau has proper support for export keyword AFAIK.
我不是这意味着贬低，但你们两个似乎都是C ++的新手，并且不知道这种语言的基本哲学。像C一样，C ++对语言特性和标准库采用了极简主义的方法，这就是允许C和C ++如此容易地移植到大量的C和C ++中的原因。很多
不同的平台。让我们逐点看看你的愿望清单：
1）线程 - 线程是一个在每个平台上都不存在的概念。很多
嵌入式系统没有线程。一些较旧但仍受支持的系统，
也没有线程。仅仅因为这个原因，为语言添加线程
是危险的。但是为了让事情变得更糟，线程在所有操作系统上都不会以相同的方式工作。有些允许不同的调度策略，有些则不允许。有些
允许时间片量化，有些则不然。有些允许调度优先级，
有些不是。有些允许信号进入任何线程，有些力信号转到特定线程，有些没有任何信号。当他们可以在pthreads的
方向上摆动手指时，标准委员会不会跳进那个焦油坑。
2）同步机制 - 即使我们忽略了第1点，这会使这个
点无实际，并且看看最简单的同步机制：互斥体。
即使是低互斥量的平台也不同。在某些平台上，互斥量
是递归的，而在其他平台上，递归调用会使你陷入僵局。在某些平台上，
互斥体可以跨进程共享，在其他平台上，你有不同的声明
来做到这一点。然后，糟糕的标准生物必须选择要包含的原始元素。信号灯？条件变量？活动？邮箱？ FIFO
队列？原子整数运算？你是否在平台上模仿它们？
本地不支持它们？由于委员会中有非常称职的人员，所以我非常不相信他们会为我做出这样的选择。
3） XML - 现在这个很容易。 XML是特定于应用程序的数据
表示。没有任何业务可以被用作语言
规范。同样，标准委员会会正确地指出你在许多现有库中的一个
。
这会不断回来，但C ++社区只是没有''我想要一个类似Java的，
臃肿，万能的杰作但是没有主人的标准库。
Claudio Puviani
I don''t mean this deprecatingly, but the you both seem to be new to C++ and
unaware of the underlying philosophy of the language. C++, like C, takes a
minimalist approach to language features and standard libraries, which is what
has allowed C and C++ to be so easily ported to a large number of vastly
different platforms. Let''s look at your wish list point by point:
1) Threads - threads are a concept that doesn''t exist on every platform. Many
embedded systems don''t have threads. Some older, but still supported systems,
also don''t have threads. For this reason alone, adding threads to the language
is dangerous. But to make things worse, threads don''t work the same way on all
operating systems. Some allow different scheduling strategies, some don''t. Some
allow time slice quantization, some don''t. Some allow scheduling priorities,
some don''t. Some allow signals to go to any thread, some force signals to go to
specific threads, some have no signals at all. The Standards committee isn''t
about to jump in that tar pit when they can just waggle their finger in the
direction of pthreads.
2) Synchronization mechanisms - even if we ignore point 1, which would make this
point moot, and look at the simplest of synchronization mechanisms: the mutex.
Even lowly mutexes are different across platforms. On some platforms, mutexes
are recursive, on others, recursive calls deadlock you. On some platforms,
mutexes can be shared across processes, on others, you have different promitives
to do that. And then, the poor Standards critters would have to choose what
primitives to include. Semaphores? Condition variables? Events? Mailboxes? FIFO
queues? Atomic integer operations? And do you emulate them on platforms that
don''t support them natively? With all respect due to the immensely competent
people on the committee, I wouldn''t trust even them to make that choice for me.
3) XML - now this one''s easy. XML is an application-specific data
representation. That has no business being shoehorned into a language
specification. Again, the Standards committee would correctly point you to one
of the many existing libraries.
This keeps coming back, but the C++ community just doesn''t want a Java-like,
bloated, jack-of-all-trades-but-master-of-none standard library.
Claudio Puviani
这篇关于下一个C ++的ISO / ANSI标准的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
