[citation needed]
The CSIRO WiFi patents have held up so far, I'm guessing a heap of really pissed already-settled Fortune 500's if there turns out to be applicable prior art. What makes you think Bell Labs IP contains the CSIRO antivenom?
By "memory access" I mean pointers, buffers etc. You can't code in C and get away from these and they are a (the?) common source of newbie programming bugs in C code.
Hells, at least Java, Ada etc have the good sense (and, yes, runtime overhead) of bitching at you when you overstep your bounds.
Well that's true up to the point that your careless memory leaks cause you to hit some threshold and are terminated! Really, I've had this happen to me in a programming contest, it sucks:-)
Maybe of more interest is the memory access part of my post - who hasn't had their C SIGSEGV'd for invalid pointer and/or buffer overrun offences?
btw I agree wrt algorithmic complexity but then I've never coded in a contest with a CPU time bound like this one apparently has..
OK C could be a computationally fast solution, but I'd go for Python anyway. Why? Mainly this: How many new C programmers (i.e. less than 1 or 2 years experience) can write programs without obscure memory leak/access problems? How much time have slashdotters wasted looking for elusive segfaults in C code? I know I've wasted hours, days, chasing buffer overruns in school assignments. Or worse are the ones you don't see; they only trigger on the examiner's machine..
surely you're going to code better if what ever you do hear is pleasing to you..
Throw in a pair of noise-cancelling headphones so you can have the music on whisper-quiet and you're set.
Slashdot Mirror
[citation needed] The CSIRO WiFi patents have held up so far, I'm guessing a heap of really pissed already-settled Fortune 500's if there turns out to be applicable prior art. What makes you think Bell Labs IP contains the CSIRO antivenom?
By "memory access" I mean pointers, buffers etc. You can't code in C and get away from these and they are a (the?) common source of newbie programming bugs in C code. Hells, at least Java, Ada etc have the good sense (and, yes, runtime overhead) of bitching at you when you overstep your bounds.
Well that's true up to the point that your careless memory leaks cause you to hit some threshold and are terminated! Really, I've had this happen to me in a programming contest, it sucks :-)
Maybe of more interest is the memory access part of my post - who hasn't had their C SIGSEGV'd for invalid pointer and/or buffer overrun offences?
btw I agree wrt algorithmic complexity but then I've never coded in a contest with a CPU time bound like this one apparently has..
OK C could be a computationally fast solution, but I'd go for Python anyway. Why? Mainly this: How many new C programmers (i.e. less than 1 or 2 years experience) can write programs without obscure memory leak/access problems? How much time have slashdotters wasted looking for elusive segfaults in C code? I know I've wasted hours, days, chasing buffer overruns in school assignments. Or worse are the ones you don't see; they only trigger on the examiner's machine..
surely you're going to code better if what ever you do hear is pleasing to you.. Throw in a pair of noise-cancelling headphones so you can have the music on whisper-quiet and you're set.