On 2007/11/28, John (Eljay) Love-Jensen <eljay@xxxxxxxxx> wrote: > Hi Duft, > > > I assume, that all strategies discussed here are targeted at C. now what about C++, how do things behave there? As far as i know C++ is much different, and requires completely different thinking with regards to splitting source in more files, etc. > > The Large-Scale C++ Software Design by Lakos which I've recommended targets C++. > > http://www.amazon.com/dp/0201633620 How to take you of care in "dangling pointers" and "memory leaks" from C++ sources? For large-scale projects, besides C++, there are another high-level languages as Java (hated people because of Sun), Eiffel, Erlang, Mercury, Oz, Common Lisp, Ruby, Python, etc. 1. http://en.wikipedia.org/wiki/Programming_language 2. http://www.dmoz.org/Computers/Programming/Languages/ 3. http://directory.google.com/Top/Computers/Programming/Languages/ 4. http://en.wikipedia.org/wiki/List_of_programming_languages 4.1 http://en.wikipedia.org/wiki/Timeline_of_programming_languages 4.2 http://en.wikipedia.org/wiki/Alphabetical_list_of_programming_languages 4.3 http://en.wikipedia.org/wiki/Generational_list_of_programming_languages 4.4 http://en.wikipedia.org/wiki/Categorical_list_of_programming_languages They aren't good idea splitting files of large-scale projects from these languages. The "maintainance" is an important issue in large-scale projects. J.C.Pizarro
