Talk:Doom source code

I'd quite like to do a file-by-file analysis of the source code. Perhaps one article per file? How should I structure/name this?

That'd be awesome. It'd probably make most sense to create one page per file and just use the file names (the only problem is that foo.c becomes Foo.c, but I think that's bearable), with overview pages as necessary. If you just get it written, it can easily be restructured later on :)

By the way, article titles and headlines should go "Foo bar baz", not "Foo Bar Baz". Fredrik 01:19, 10 Jan 2005 (PST)

Actually on second thoughts I may just put it all on a single page. I'm really not sure I can say that much about each file for it to be worth doing a page for each. If neccessary I can add separate pages for subjects which need more in-depth attention. Like you say, we can always restructure it if neccessary.

That would be most excellent if it happened. If I can make a suggestion, any knowledge on how the files actually link together, ie what calls what and when, as well as how mods integrate with the retail doom (as retail doom is required for them to run) would be much appreciated. A flow-chart or something similar would really open doors to those just starting to dabble with the code. MithTS 22:32, 13 Mar 2006 (EST)