走PL / 1方式 [英] Going the PL/1 way
问题描述
好的，好像我们有@decorators。对Intercal来说，这是一个很好的致敬。但是
我更喜欢#decorators。
我们有用于快乐大脑融化的元类。我们有生成器，
新式课程和旧式课程。 Lambdas很棒。
我们确实需要真正的接口，而不是滥用的类。 Python仍然需要内联函数，宏和模板。运算符重载是不够的，
应该能够自由地引入新的。对于
的比较，需求量很大。为什么我们没有''案例'陈述和''做...重复
（）''？
我们离不开一般的封闭，当然。嗯，自动垃圾
集合有时候很好但是明确的内存分配/解除分配对于高效的程序来说真的是不可避免的。
等等，指针是一个必须！静态打字应该在很久以前推出了很长的
。你不能没有绝对的地址变量。
是的，我对匍匐的特征主义感到厌烦。
$ b $bMiklós
Miklós写道：
好吧，好像我们有@decorators。对Intercal来说，这是一个很好的致敬。但是
我更喜欢#decorators。
我们有用于快乐大脑融化的元类。我们有发电机，新式班级和旧式班级。 Lambdas很精彩。
我们确实需要真正的接口，而不是滥用的类。 Python仍然需要内联函数，宏和模板。操作员超载是不够的，
应该能够自由地引入新的。对于比较进行比较，需求量很大。为什么我们没有''案例'陈述和''重复
（）''？
当然，我们离不开一般的封闭。嗯，自动垃圾收集有时候很好，但对于高效的程序来说，明确的内存分配/解除分配是非常不可避免的。
等等，指针是必须的！静态打字应该已经介绍了很久很久以前。你不能没有绝对的地址变量。
是的，我对匍匐的特征主义感到厌烦。
男人，你偷我的想法！
2.1之后制作成Python的大多数功能都是只是那个，比如
没有人拥有它，所以我们应该或有人拥有它，所以我们也会。
我在2.3中唯一受欢迎的是一些翻译加速，而不是新功能。
真的是非常需要的功能，干净，紧凑和可读的
规则应该被打破？该死的，还有装饰师的地狱，我甚至都不知道
知道什么是好的。
来吧，伙计们，解决像翻译线程这样的真正问题安全，提高
性能，不要让我们，现实世界的软件开发人员，请每个新版本尖叫
。
< br $>
-
Jarek Zgoda
http://jpa.berlios.de/
Jarek Zgoda< jz **** @ gazeta.usun.pl>写道：
来吧，伙计们，解决真正的问题，如翻译线程安全，提高性能，不要让我们，真实世界的软件 >开发人员，请为每个新版本尖叫。
http://www.python.org/patches/
干杯，
mwh
-
Monte Carlo采样无法理解代码。
- Gordon McMillan，comp.lang.python
" Jarek Zgoda" < JZ **** @ gazeta.usun.pl>在消息中写道
news：cf ********** @ nemesis.news.tpi.pl ...Miklós写道：
是的，我对匍匐的特征主义感到厌烦。
男人，你偷了我的想法！
2.1之后制作成Python的大部分功能都是 ;只是那个，就像
没有人拥有它，所以我们应该或有人拥有它，所以我们也会。我在2.3中唯一欢迎的是一些翻译加速，而不是新的
功能。
是否真的非常需要的功能，干净，紧凑和可读的
规则应该被打破？该死的，还有装饰师的地狱，我知道甚至没有人知道它有什么好处。
来吧，伙计们，修复解释器线程安全等真正的问题，提高性能请不要让我们，现实世界的软件开发人员，请每个新版本尖叫。
是的，这正是我的观点。性能和GIL。这些都是问题。
问题必须解决。之后添加功能...如果他们真的需要
。
$ b $bMiklós
-
Jarek Zgoda
http://jpa.berlios.de/ / blockquote>
Ok, seems like we have @decorators. It''s a nice tribute to Intercal. But
I''d prefer #decorators.
We have metaclasses for pleasure brain-melting. We have generators,
new-style classes and old-style classes. Lambdas are wonderful.
We do need real interfaces, not abused classes. Python still needs to have
inlined functions, macros and templates. Operator overloading is not enough,
one should be able to introduce new ones freely. There''s a heavy demand for
terciary comparisons. Why don''t we have a ''case'' statement and ''do... repeat
()''?
We cannot do without general closures, of course. Hm, automatic garbage
collection is sometimes fine but explicite memory allocation/deallocation is
really unavoidable for efficient programs.
Wait, pointers are a must! Static typing should have been introduced a long
time ago. You just cannot do without absolute address variables.
Yes, I''m thorougly annoyed with creeping featurism.
Miklós
解决方案Miklós wrote:
Ok, seems like we have @decorators. It''s a nice tribute to Intercal. But
I''d prefer #decorators.
We have metaclasses for pleasure brain-melting. We have generators,
new-style classes and old-style classes. Lambdas are wonderful.
We do need real interfaces, not abused classes. Python still needs to have
inlined functions, macros and templates. Operator overloading is not enough,
one should be able to introduce new ones freely. There''s a heavy demand for
terciary comparisons. Why don''t we have a ''case'' statement and ''do... repeat
()''?
We cannot do without general closures, of course. Hm, automatic garbage
collection is sometimes fine but explicite memory allocation/deallocation is
really unavoidable for efficient programs.
Wait, pointers are a must! Static typing should have been introduced a long
time ago. You just cannot do without absolute address variables.
Yes, I''m thorougly annoyed with creeping featurism.
Man, you steal my thoughts!
Most of features that made into Python after 2.1 are "just that", like
"nobody has it, so we should" or "somebody has it, so we would too". The
only thing I welcomed in 2.3 was some interpreter speedup, not new features.
Is it really so much needed feature, that "clean, compact and readable"
rule should be broken? Damn, to hell with decorators, noone I know even
knows what it can be good for.
Come on, guys, fix real problems like interpreter thread safety, improve
performance, don''t make us, "real-world software developers", screaming
with every new release, please.
--
Jarek Zgoda
http://jpa.berlios.de/
Jarek Zgoda <jz****@gazeta.usun.pl> writes:
Come on, guys, fix real problems like interpreter thread safety,
improve performance, don''t make us, "real-world software
developers", screaming with every new release, please.
http://www.python.org/patches/
Cheers,
mwh
--
Monte Carlo sampling is no way to understand code.
-- Gordon McMillan, comp.lang.python
"Jarek Zgoda" <jz****@gazeta.usun.pl> wrote in message
news:cf**********@nemesis.news.tpi.pl...Miklós wrote:Yes, I''m thorougly annoyed with creeping featurism.
Man, you steal my thoughts!
Most of features that made into Python after 2.1 are "just that", like
"nobody has it, so we should" or "somebody has it, so we would too". The
only thing I welcomed in 2.3 was some interpreter speedup, not new
features.
Is it really so much needed feature, that "clean, compact and readable"
rule should be broken? Damn, to hell with decorators, noone I know even
knows what it can be good for.
Come on, guys, fix real problems like interpreter thread safety, improve
performance, don''t make us, "real-world software developers", screaming
with every new release, please.
Yes, this was exactly my point. Performance and GIL. Those are problems.
And problems must be solved. After that add features... if they are really
needed.
Miklós
--
Jarek Zgoda
http://jpa.berlios.de/
这篇关于走PL / 1方式的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
