|
|
|
| Pure Allegro Competition returns after 2 years. |
|
23yrold3yrold
Member #1,134
March 2001
 |
You could have just been a little more flexible with your rules, you know. Oh well ... -- |
|
spellcaster
Member #1,493
September 2001
 |
Maybe, just maybe, 2 years ago, the idea of cdding style, readavle code, etc. where not that common? I still don't get the point. If you want to see what one can do using allegro only, all you need is a single rule: 1) You may not use any functions (or macros) besides those provided by allegro or those you have written yourself during the compo. I think that would work well Regarding using the pre-proc before submitting: My whole point is that it's pretty ppointles. But using macros you could at least make your code slightly more structured. Using Macros you could for example create a human readable state machine inside your main loop, including "methods" to put parameters on the stack which could then be fetched again by the states, etc. And, after looking at your code, I had another idea how to circumvent the restructions...
In combination with a global stack and some parameter vars, this would work nicely as well. As you can see, providing too many obstacles which are not even related to the actual goal ("pure allegro"), just to prevent cheating will do your compo more harm. -- |
|
Siloh
Member #2,786
October 2002
|
From what I can tell, most people just did not like it because they personally felt that the rules were too strict for them or were too messy for their style, and hence decided to just flame it instead. And I haven't seen code like yours for a very long time, it is not that I just wanted to stop cheaters, I wanted to see how people would find other ways to do things when they couldn't just write 50 functions with commonly documented algorithms to replace those in the C library. We actually had a good time talking about this on IRC, for example using create_bitmap or create_sample to replace malloc, may seem extremely hackish and taboo, but it would still be interesting to see how other Allegro functions could be used to make a working program or game. Obviously only a few people shared such an interest. |
|
spellcaster
Member #1,493
September 2001
|
Quote: We actually had a good time talking about this on IRC, for example using create_bitmap or create_sample to replace malloc, may seem extremely hackish and taboo, but it would still be interesting to see how other Allegro functions could be used to make a working program or game.
Then maybe telling us something like that would have been a good idea as well? I asked for your motivation quite some time ago, and that's the first time you replied to it. Quote: I wanted to see how people would find other ways to do things when they couldn't just write 50 functions with commonly documented algorithms to replace those in the C library. You won't need that many functions with algos anyway. But it's nice to reuse code, it's nice to reduce code clutter etc. For memory allocations, I'd still say that creating one or 2mb big array and managing handles to that memory yourself would work equally well. Combine that with the state machine approach to simulate functions calls, and you could even create more complex games. Quote: but I will most likely host a much less complex competition in December
Less complex? Or did you mean "less messy"? -- |
|
|
|
