Okay, there is how this works:
You must post legal C code, in such a way that if I were to stick it all in one file, with appropriate function prototypes so that order doesn't matter, the only errors it gets is linker errors for undefined functions. What that means, is use legal C syntax, and throw in descriptively-named functions wherever you don't feel like writing the details.
In theory, what we will end up with, once all of the placeholder functions are written, is the most unexpected mass of feature-creep that is still barely able to compile.
Example: I define
int main(int argc,char *argv[])
{
doStartup(argc,argv);
while(keepRunning())
{
loopCode();
}
doEndStuff();
}Then someone else starts adding to it, with
void loopCode()
{
log_text("Ohai\n");
calculate_physics(&player);
create_enemies();
do_input_stuff();
draw_it_all();
}
Then as paeople go along, the end result is a crazy collection of diffrent styles, intentions and other stuff that makes countless memeory leaks, the occasional core dump, and a great example of what NOT to do.
Finally, with common consent, earlier code may be edited for any reason.
Okay, lets start.
We must decide between win32, console, or other, as it will greatly impact the potential features.
Only limit is that it must be commnly available C, and as a bare minimum, compiled on windows with MinGW and less than 10 MB of external library downloads(If everybody agrees, any of these limits may be negated, or new ones added).
Author
Topic: Game for programmers: Pseudocode chaos (Read 1687 times)