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:
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
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:
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
Comment