> The only plausible reason I can think of for this approach, is that the people
> involved aren't comfortable with makefiles, and don't want to admit weakness.
> There are plenty of folk spoiled by IDEs in this camp.
> If you pull in all your .c files via #includes, what this buys you is that you
> can use a single makefile, never have to add new modules to it.
> On the downside, you completely screw your namespace; you can't use private
> variables or private helper functions - everything is effectively global.
> And the compile time will be horrible, of course.
> Anyway, my advice to you is:
> 1. avoid being confrontational; for better or worse, you have to work with these
> 2. stick with objective arguments (i.e. total compile time, namespace issues);
> anything resembling a religious argument will get you shut down
Will do - I think what I've decided to do is make a written dated record of what I was accused of at this meeting by this guy, because there were a couple of allegations that were simply false - for example that I was using the function malloc() in the game code instead of the companies memory allocation functions, which isn't true, and by doing that I was affecting the Sony Technical Requirements and the game would fail. (What's it called? I could do with putting the official name on this Doc, is it the Sony T.R.I., or T.R.C. or something?)
I could note down in the same document the thigns about the #including, compile time, namespace issues, the resultant compiler crash output with a date etc.
> 3. if at all possible, show proof of concept of something better, and do it in
> your own time
You learn something old everyday...