A friend pointed out how the pseudo-code for some article he was reading was hard to understand. If we're going to use pseudo-code for articles, shouldn't there be a pseduo-code standard so we can all understand it?
I'd imagine it could look something like C, or any other widely used language, and at least TRY to incorporate most of the things common to all or a majority of programming languages.
Personally i feel all articles should just demonstrate stuff in C but you can't force your personal views on languages onto others so that's why i think there should exist some sort of lose standard for pseudo-code in articles and tutorials.
Who better to develop it than a message board full of pseduo-programmers. Get to it /prog/!
Also, wtf is this shit?! Fatal error! Message could not be posted.
Please post threads less often!
Clearly we should use Lisp, since it has the fewest arbitrary rules for our pseudocode to follow. Or else we could follow Knuth and use Enlish as our high-level language.
Name:
Anonymous2007-12-17 17:16
>>7
I named my dog Haskell precisely because he's useless.
Name:
Anonymous2007-12-17 17:53
>>17
This thread is now about suitable /prog/ pet names. I've actually been wanting to do a thread like this for a while now, but I can only make one thread per week.
Suitable pet names:
Haskell
Kernighan
Ritchie
Radix
Name:
Anonymous2007-12-17 18:34
>>18
"Good for nothing piece of shit" would be a good pet name, since any /prog/rammer worth his salt calls his machine/language/etc that on a regular basis.
Name:
Anonymous2007-12-17 18:38
>>19
No, that's a horrible name for a /prog/ pet :(