Julie wrote:
"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.
Have you looked at the NASA SEL?
I looked at that a *long* time ago, and don't remember anything about it,
but it just popped into my head...
This is a living example of one of the most successful C++ dominated
software projects ever:
http://www.mozilla.org/projects/
I recall looking at the NASA site a while back as well. The kind of stuff
I'm looking for is not the high-level abstraction, how to design your
interfaces between packages, etc., kind of literature. I want more
fundamental guidance on how to use the plethora of alternatives provided by
the features described in the Standard. I just read through Clause 3
(Chapter 3) of PL-C++03. This is out of date, but it will give a hint of
what the current document reads like. The stuff on name lookup is
mind-boggling.
http://www.itga.com.au/~gnb/wp/cd2/
I do have a way of establishing a pretty powerful project structure in a
hurry. The KDE and KDevelop are doing a wonderful job. Unfortunately, some
of the outstanding performance is due to the contributions of uniquely
tallanted people, and not a codified approach. But it is open to
examination:
http://ng-project.org/~kdevelop/apid.../inherits.html
The following is from a 'hello world' created by KDevelop:
hattons@ljosalfr:~/code/c++/managed/
Wed Apr 07 04:30:01:> find . -name "*"
..
../po
../po/Makefile.am
../po/Makefile.in
../doc
../doc/en
../doc/en/Makefile.am
../doc/en/Makefile.in
../doc/en/index.docbook
../doc/Makefile.am
../doc/Makefile.in
../src
../src/hi16-app-managed.png
../src/managed.cpp
../src/managed.lsm
../src/main.cpp
../src/managed.h
../src/Makefile.am
../src/Makefile.in
../src/managedui.rc
../src/hi32-app-managed.png
../src/managed.desktop
../NEWS
../TODO
../admin
../admin/CVS
../admin/CVS/Root
../admin/CVS/Repository
../admin/CVS/Entries
../admin/CVS/Template
../admin/compile
../admin/Doxyfile.global
../admin/depcomp
../admin/Makefile.common
../admin/ltmain.sh
../admin/config.pl
../admin/configure.in.min
../admin/config.guess
../admin/acinclude.m4.in
../admin/install-sh
../admin/config.sub
../admin/missing
../admin/mkinstalldirs
../admin/cvs.sh
../admin/bcheck.pl
../admin/nmcheck
../admin/conf.change.pl
../admin/am_edit
../admin/libtool.m4.in
../admin/ylwrap
../admin/cvs-clean.pl
../admin/debianrules
../admin/detect-autoconf.sh
../admin/ChangeLog
../admin/Doxyfile.am
../admin/configure.in.bot.end
../debug
../debug/po
../debug/po/Makefile
../debug/doc
../debug/doc/en
../debug/doc/en/Makefile
../debug/doc/en/index.cache.bz2
../debug/doc/Makefile
../debug/src
../debug/src/Makefile
../debug/src/.deps
../debug/src/.deps/managed.Po
../debug/src/.deps/main.Po
../debug/src/.libs
../debug/src/managed.moc
../debug/src/managed
../debug/src/managed.o
../debug/src/main.o
../debug/Makefile
../debug/config.status
../debug/libtool
../debug/config.log
../debug/config.h
../debug/stamp-h1
../aclocal.m4
../README
../configure
../autom4te.cache
../autom4te.cache/requests
../autom4te.cache/output.0
../autom4te.cache/traces.0
../configure.in
../subdirs
../Makefile.am
../Makefile.in
../configure.files
../configure.in.in
../config.h.in
../Makefile.cvs
../acinclude.m4
../managed.kdevelop
../stamp-h.in
../AUTHORS
../INSTALL
../ChangeLog
../COPYING
../Doxyfile
../templates
../templates/h
../templates/cpp
hattons@ljosalfr:~/code/c++/managed/
But, now I want to pull in stuff from boost, and Xerces. I know some of
it's just a question of time and experience, but there also seems to be
something fundamentally missing that would pull everything together. I'm
trying very hard not to draw comparrisons, but I've see some aspects of
programming managed more effectively than a lot of C++ stuff.
--
p->m == (*p).m == p[0].m
http://www.kdevelop.org http://www.suse.com http://www.mozilla.org