I'm sure this was brought up in the past, but DMD definitely needs stable
and unstable branches.
-v1 doesn't cut it. My code is compiled with -v1 and still breaks with new
DMD versions.
Each new DMD version is bug-ridden. This new one 1.011 is pretty bad!
How am I supposed to let others use my code when there's no stability in
the compiler? They update their compiler and report to me "your code is
broken"; well, no, DMD is broken.
I have a ton of code that doesn't work on any of the new DMD compilers; I
have to use an old pre-1.0 compiler, because the recent compilers are
bug-ridden. Some bugs get fixed, but even more get added.
I'm sure a lot of you out there have similar experiences. Speak up now,
please!
With each new release I get more and more frustrated with D. There's no
stability! I know you want more and more features, but how can I keep
using a language like this?
-
I know, I know, report bugs. This doesn't cut it. Reporting bugs is hard
as hell and time consuming. I need time to report bugs. Now I have to
either restrict use to specific compiler versions, which people don't
always know about and report their issues back to me, until I remind them
they need to downgrade their compiler (which isn't always an option if
they need bug fixes), or I have to rush to fix my code to workaround such
issues and report bugs. If there was a stable branch, I could get the code
working with the unstable branch at a reasonable pace.
-
D 1.0 means nothing. The 1.0 release was a huge flop. I think it could
have done so much better and retained more users. We need some stability
and to try the big release one more time. "D 1.1 release 'whoops, got it
right this time'" (hopefully).
Also, the documentation should probably clearly state differences between
versions, perhaps even with the words "unstable" near the things not in
the stable branch. (Safe to ignore 1.0 since it's pointless.)
-
I've had all this in the back of my mind for quite some time and I've
tried to be patient about it. I'm not trying threaten anyone, but I don't
know how much longer I'm going to put up with D with its current methods.
Note that I am probably one of the oldest D users still using it.
-
Thanks for your time.
- Christopher E. Miller
回顾D语言走的崎岖之路1
分享到:
相关推荐
GB/T 21010-2007 土地利用现状分类
GB/T 21010—2007《土地利用现状分类》
幼儿园语言活动的现状、问题及策略.zip
自然语言处理的现状与未来PPT课件.pptx
李航教授展望自然语言对话领域:现状与未来.pdf
随 着软件 体 系结 构在 软件 开发 中 作 用 的 不 断提 高 和 近 期来软 件 体 系 结构 概念 的 明 确 提 出 ,要 求为 其表 示 和分 析 开发专 门 支 持 工 具 和 环 境 的需 求也越来 越 迫切。
本次会议主要关注生成式大语言模型的发展与现状。文档介绍了自然语言处理(NLP)在人工智能皇冠上的“明珠”,并探讨了语义消歧、抽象语义表示分析、语义角色标注、词汇/句子/段落向量表示框架、框架语义分析、一阶...
数据挖掘系统需要的一个功能是支持临时和交互式数据...可以设计数据挖掘查询语言来支持这一功能,除了数据挖掘查询语言,数据挖掘语言也包括数据挖掘建模语言与通用数据挖掘语言,文章将分别阐述它们的特点,并进行比较。
硬件描述语言HDL的现状与发展.基于SystemC和Verilog软硬件协同验证.vhdl verilog system verilog systemc等
幼儿园小班语言游戏现状分析.docx
讨论JAVA语言的现状及发展.pdf
全球疫苗产业发展现状分析2007.docx
浅析Java语言的生存现状.pdf
幼儿园语言教学课堂提问的现状与策略.zip
java语言的发展现状及趋势
语料库语言学研究发展现状浅析
关于数据挖掘语言应用现状的分析.pdf
广播电视播音主持语言的现状及建议.docx
中文自然语言处理的现状与展望 • 数据资源 • 技术评测 • 基础技术 • 应用技术 • 总结与展望
通过对高新技术企业R&D(Research and Development)税收激励政策现状与问题的分析和总结后,发现现有税收政策体系与高新技术企业R&D活动特点结合不够,是造成税收激励政策体系散乱、激励力度不够和研发税收实务操作难等...