Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Libre Office not good enough for you?
LOL. Care to make it interesting? Unlike most assholes here, I don't just say shit to make myself feel good, I'll back it up with cash. Care to wager some money that the GOP will take the White House in 2 years?
My use of goto sounds like everybody else's: if(something_bad_has_happened) goto code_to_fix_it;
In highly modular code with lots of procedures the "goto" may end up as a longjmp(). So be it.
More importantly though, at some point after Fox kicked him to the curb he retooled his show into something more "Morning Zoo"-esque, and it's just not the same. Man's lost his park.
Yes, they did.
In another job interview I was asked to write a program to generate prime numbers. I clarified a couple of requirements ("is memory usage an issue?"), and implemented the Sieve of Eratosthenes. It works, you know why it works, any idiot can read the code and understand it, and if testing shows you need something better (in some sense), you know where to start.
Regardless of the final implementation, there are problems where the simplest, clearest solution is a recursive one. You type it in to the computer as fast as you can type, it compiles and runs correctly the first time, and then, if you need to change it, you have a place to start.
On a job interview some years ago I was asked to write C code to reverse a string. I wrote it recursively: interchange the first and last elements, then reverse what's inside.
They liked my creativity. I got the job.