void cnfsave()
I knew it. This kind of store-the-state-in-an-array code is usually begotten because someone wants to be clever and simplify saving/loading.
And always with magic numbers, because that's how it was done in BASIC, where they first learned the technique.
Name:
Anonymous2010-08-16 20:15
That is some of the shittiest code I've ever seen.
And if you're Japanese, won't you be forced to use Ruby?
Name:
Anonymous2010-08-18 4:12
I had a Japanese professor for a couple CS classes and noticed he like 2-5 letter variable wherever possible, often giving things that should have been "blockOn" names like blkn
I had a Nipponese sensei for a couple of conpyuta sciensu classes and noticed he like the dibagga wherever possible, often giving things that should have been "traceOn" names like yelling TRACE ON!!! and jamming his p○n○s into my vag○○○ to replenish my magic
>>35
Is that even relevant to this thread, or just your way of saying ``I have read SICP to learn how to write spam bots''?
Name:
Anonymous2010-08-19 3:52
>>1
At first glance, I thought this was C, but what the hell is an alt statement? And why do all the case statements look like: case e7==something: where "e7" is not defined anywhere?
>>37
Macros and globals respectively. It's only a snippet.
Name:
Anonymous2010-08-19 4:23
>>33
I'm not talking about the braces dumbass. I'm talking about case e7==0:. That is completely fucked. Without macros, that's a boolean, and there are only two values of it. Cases cannot be repeated and have to be compile-time constants.
The only way this can compile as C is if e7 is some crazy-ass macro. The case statements also have no breaks, so unless case is also overridden, or e7 contains a break and opens a new case, then all these case statements fall through.
>>38
You're going to need to give us the macros for alt and e7, and possibly case as well if it's overridden by a macro.
>>39 I'm not talking about the braces dumbass. I'm talking about case e7==0:. That is completely fucked. Without macros, that's a boolean, and there are only two values of it.
Maybe you should actually look up how C works.
Cases cannot be repeated and have to be compile-time constants.
Maybe you should also look up how labels work in general.
Anyway.
Did Satoshi Nishimura write this code? Sure looks like his.