Re: [glob2-devel] coding guidlines

[Bradley Arsenault]

True, while free-reign documenting may have ended with some bad results in the past, our programmers, including myself and stephane, are more experienced and much more willing to document and organize properly.

Also, separating those files into the 60 or 70 different files for each individual class will drastically increase the compile times, since each file will require a different compiler call, and cost the overhead of compiling header files that each individual file includes. As far as compile times are concerned, I have gone through the headers a few times now and tried to eliminate unnecessary includes that where causing files to be recompiled when they didn't need to be. It was quite successful, I shaved off a couple minutes from average compile time on my old computer.

I only mentioned wasteful in terms of splitting those two particular files, and files like them, into separate files. These files are also modified by scripts, the add_whatever.py scripts, which make augmenting those files with another class a very quick proccess. They are in one file because for the most part they are identical, tiny classes, all of the classes come together and serve a single idea.

I think that moving the source files into an organized folder hierarchy isn't a bad idea. I don't personally have a problem with the one folder layout, I've navigated it quite quickly and have learned to use it very efficiently, but the same could be done in a deeper folder layout. I don't like seperating source files from header files as in libgag, I've only found this to be fustrating and not really improving to organization. Categories on the other hand, like "YOG" or "Engine" is fine.

-- 
Extra cheese comes at a cost. Bradley Arsenault.