《大规模 C++ 程序设计》封面

大规模 C++ 程序设计

Large-scale C++ software design

John Lakos · 初版 1996 年

24人推荐
34位读者提及
41次提及

为什么值得读

  • 提供减少文件依赖的具体指标与设计指南
  • 总结源自实战的大型系统编译耗时优化技术
  • 全面探讨跨模块架构与代码组织的实际原则

Hacker News 上怎么说

  • 我不是 C/C++ 专家,但我强烈推荐 John Lakos 的《Large-Scale C++ Software Design》这本书。它深入探讨了如何组织程序架构,除了详细解答上述问题外,还覆盖了许多其他痛点。我很想听听 HN 上其他…的看法

    I'm not a C/C++ expert but I can highly recommend the book "Large-Scale C++ Software Design" by John Lakos. It gives an extensive discussion on how to structure programs and addresses the issue above in detail, in addition to many others. I'd be very interested to hear the opinions of any HN…

  • …依赖树,看看能不能发现什么扎眼的地方。或者你也可以手动批量“touch”几个文件,重新 build,用这种排除法揪出元凶。另外,推荐读读 John Lakos 的《Large-Scale C++ Software Design》,里面提供了很多指标和设计指南,用来降低项目中文件间的依赖度。假设你绕不开每个源文件都包含大量头文件的情况,很多 C/C++ build 工具…

    …dependency tree and see if anything jumps out at you. Alternately, you can "touch" a few files at a time manually, re-build, and try to track down a culprit that way. Also, take a look at John Lakos' "Large-Scale C++ Software Design", which offers metrics and design guides for reducing dependencies among files in a project. Assuming you have no way to get around each source file including lots of headers, many C/C++ build tools…

  • …需要考虑。还有诸如内存管理、logging 和 instrumentation 这些横切关注点。帖子末尾提到的那些设计原则,在《Large-Scale C++ Software Design》里有更好、更全面的阐述:http://www.amazon.com/Large-Scale-Software-Design-John-Lakos... 书中关于语言特性的某些观点反映了成书时 C++ 实现的不成熟,但那些设计准则…

    …consideration. There are cross-cutting concerns such as memory management, logging, and instrumentation. The design principles at the end of the post are better and more comprehensively covered by "Large-Scale C++ Software Design": http://www.amazon.com/Large-Scale-Software-Design-John-Lakos... Some of the language points in that book reflect the immaturity of C++ implementations when the book was written, but the design guidelines…

  • …视角。而且面对某些问题时,似乎存在一种“复杂度守恒”的现象。复杂度是系统内生的,端看你把它推到了哪个环节。至于书的话,你可以看看《Large-Scale C++ Software Design》。可惜我把书落在家里了,没法翻开核对,但印象里它通篇都是关于组织代码结构以及大中型软件项目布局的建议。

    …perspectives. Also with some problems there seems to be a conservation of complexity notion. It's inherent in the system and depends on where you push it. For the book, you might want to check out Large-Scale C++ Software Design. Unfortunately it's at home so I can't crack it open and double check, but it seemed full of suggestions on structuring code and layout a large software project.

  • 如果 C++ compile time 是个困扰而且/或者阻碍了生产力,我推荐 Lakos 针对该主题的开山之作:《Large-Scale C++ Software Design》[0]。书里提出的技术都源于实战经验,能显著改善大型系统的 build times。不可否认,这本书确实有些年头了,可能无法完全适用于…

    If C++ compile time is a concern and/or impediment to productivity, I recommend the seminal work regarding this topic by Lakos: Large-Scale C++ Software Design[0] The techniques set forth therein are founded in real-world experience and can significantly address large-scale system build times. Granted, the book is dated and likely not entirely applicable to…

  • * David Hanson:《C Interfaces and Implementations》* David Hanson:《A Retargetable C Compiler》* John Lakos:《Large-Scale C++ Software Design》* VA:《Beautiful {Code, Data, Testing}》* 也许还可以看看设计模式的书* 《Code Complete》* Fred Brooks:《The Mythical Man Month》* Fred Brooks:《Design of Design》* 像《C++ Pearls》或者《More…》这类“精选集”书籍

    * David Hanson: C Interfaces and Implementations * David Hanson: A Retargetable C Compiler * John Lakos: Large-Scale C++ Software Design * VA: Beautiful {Code, Data, Testing} * Design pattern books maybe * Code Complete * Fred Brooks: The Mythical Man Month * Fred Brooks: Design of Design * "Best of" books like C++ Pearls or More…

正在加载完整评论……

键盘快捷键

/
聚焦搜索框
j / k
下一本 / 上一本
Enter
打开选中的书
Esc
关闭 / 返回
g h
回到首页
g b
值得读精选
g t
历史总榜
g r
上升最快
g l
我的书架
?
显示本帮助