关于结构化（大规模）项目的任何权威参考？ [英] Any authoritative reference on structuring (large-scale) projects?
问题描述
是否有或多或少接受的权限描述如何构建
项目？我知道朱莉已经询问了名称空间。这肯定是我问题的一部分，但我想知道整个情况。
如果这样的事情不存在，那么如果某人有足够的名字
承认有影响，请判定这样的指导方针。我会很高兴能够简单地说我的项目是按照这里的[地名]建议来确定的。
KDE有一种方法，Mozilla也是如此，我相信GNOME也有某种被禁止的结构。也许我最好的选择是检查这些项目
并选择我认为有用的项目。我想有一些感觉
，我的项目的组织方式使得b / b
其他程序员可以轻松理解，这些程序员拥有广泛接受的约定。我也希望我的
工作能够顺畅地融入其他人的工作。
我坚信即使是最小的项目也应该
符合可扩展的约定。我想养成做正确的事情的习惯，但我真的不知道什么是正确的。
Stroustrup提供了一些关于这些的讨论
TC ++ PL（SE）最后章节中的问题。他的推荐被大量的b $ b b程序员采用了吗？我还没看过章节。它们是否足够透明
为组织大型项目提供了坚实的基础？
Maven是我从前世认识的东西：<
http://maven.apache.org/
实际上，我的目的实际上有点过于广泛。我只是把它作为我正在寻找的那种东西的例子。
-
p- > m ==（* p）.m == p [0] .m
http ：//www.kdevelop.org
http：//www.suse。 com
http://www.mozilla.org
Is there a more or less accepted authority describing how to structure a
project? I know Julie has asked about namespaces. That is certainly a
part of my question, but I want to know about the whole picture.
If such a thing doesn''t exist, then would someone with enough name
recognition to have an influence please decree such a guideline. I''d be
happy to simply be able to say my project is organized in accordance with
the [place name here] recommendation.
The KDE has an approach, so does Mozilla, I trust GNOME also has some kind
of proscribed structure. Perhaps my best bet is to examine these projects
and select what I find useful from each. I would like to have some sense
that my projects are organized in such a way as to be readily understood by
other programmers who share widely accepted conventions. I also want my
work to integrate smoothely with other people''s.
I''m a firm believer in the idea that even the smallest project should
conform to extensible conventions. I want to get in the habit of doing
things right, but I don''t really know what right is.
Stroustrup provides some discussion of these issues in the final chapters of
TC++PL(SE). Have his recommendations been adopted by a large number of
programmers? I have not yet read the chapters. Are they thorough enough to
provide a solid foundation for organizing a large-scale project?
Maven is something I am aware of form a past life:
http://maven.apache.org/
It''s actually a bit too broadly focused for my purposes. I''m only
presenting it as an example of the kind of thing I''m looking for.
--
p->m == (*p).m == p[0].m
http://www.kdevelop.org
http://www.suse.com
http://www.mozilla.org
推荐答案
Steven T. Hatton写道：
< snip>
Steven T. Hatton wrote:
<snip>
Stroustrup在TC ++ PL（SE）的最后章节中对这些问题进行了一些讨论。他的建议是否被大量程序员采用？我还没看过章节。它们是否足够彻底，为组织大型项目奠定了坚实的基础？
Stroustrup provides some discussion of these issues in the final
chapters of TC++PL(SE). Have his recommendations been adopted by a
large number of programmers? I have not yet read the chapters. Are
they thorough enough to provide a solid foundation for organizing a
large-scale project?
当我看到这些章节时我想到了这些章节主题文本。我强烈建议您阅读章节中的
;他们是非常好的IMO。
- Pete
< snip>
I thought of these chapters when I saw the subject text. I highly suggest
you read the chapters; they''re very good IMO.
- Pete
<snip>
Steven T. Hatton写道：
< snip>
Steven T. Hatton wrote:
<snip>
Stroustrup在TC的最后章节中讨论了这些问题++ PL（SE）。他的建议是否被大量程序员采用？我还没看过章节。它们是否足够彻底，为组织大型项目奠定了坚实的基础？
Stroustrup provides some discussion of these issues in the final
chapters of TC++PL(SE). Have his recommendations been adopted by a
large number of programmers? I have not yet read the chapters. Are
they thorough enough to provide a solid foundation for organizing a
large-scale project?
当我看到这些章节时我想到了这些章节主题文本。我强烈建议您阅读章节中的
;他们是非常好的IMO。
- Pete
< snip>
I thought of these chapters when I saw the subject text. I highly suggest
you read the chapters; they''re very good IMO.
- Pete
<snip>
Steven T. Hatton写道：
Steven T. Hatton wrote:
是否有一个或多或少被接受的权威描述如何构建一个
项目？我知道朱莉已经询问了名称空间。这当然是我问题的一部分，但我想知道整个情况。
Is there a more or less accepted authority describing how to structure a
project? I know Julie has asked about namespaces. That is certainly a
part of my question, but I want to know about the whole picture.
这些主要是软件工程问题。
您可以尝试
大规模C ++软件设计作者：John Lakos。
http://www.amazon.com/exec/obidos/tg...29721?v=glance
但是小心。它于1996年7月发布
并包含一些过时的建议。
These are mostly Software Engineering issues.
You might try
"Large-Scale C++ Software Design" by John Lakos.
http://www.amazon.com/exec/obidos/tg...29721?v=glance
But be careful. It was published in July 1996
and contains some out-of-date recommendations.
这篇关于关于结构化（大规模）项目的任何权威参考？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
