usually i try to as well, but i like simliar functions in the same included files

but sometimes happens so that i need alot of functions in a single include.
i've been bitched at by 4 people so far on how i code in Pro, and two others just arn't really fond of how i lay things out ... because i set everything up as if its in like C
so i have Header's with Types/Contants/Functions
i then have CodeSource's which are full of functions that are more program specific ... finally i have a layer of Direct Link Source which is the main programs - then its all tied into a main program CodeSource
i mean with the DBpro/DarkEdit editors i can kinda understand why people don't like it, because its not really greatly easy to see what is where and everything - but i find it so much easier to keep everything neat, and contain bugs easier ... cause i can just cut out sections of code in a single source, no worries cause nothing else is affected - so no trawling through source just to find a small section that could've messed up.
also been kinda pee'd upon about the fact i also use the type designation, rather than using straight variables - but i dunno how people remember so many variables in thier programs nameing them a,b,x,h etc...
ho hum i dunno

its funny really cause for the size of the programs, you have like 1,000-3,000 maybe less lines of code which will actively be run per loop ... you just have everything else there from libraries you make, other functions which will can be used later if needed - plugin support
games generally won't get really quite as high as most of the things i develop, however Black&White has i think 10,000 lines of Ai basecode and more thats create per creature which is autoscripted whilst playing.
hehee but this is like an amature community mostly, so don't expect anyone to go overboard - i think games that hit around 4,000 lines is roughtly right for most games around here

anything with complexities of say Quake2 will probably get as high as 6,000 perhaps
Tsu'va Oni Ni Jyuuko Fiori Sei Tau!
One block follows the suit ... the whole suit of blocks is the path ... what have you found?