Well, I'm hard pressed to think of a language where this IS correct.
In C, C++, VB, Pascal/Delphi, Haskell, Python, Ruby (and Perl too, I bet): 2b is neither a valid number ("b" is not a digit unless you use 0xN, $N or other hex notations) nor a valid identifier (variables, constants and function names must start with a letter or an underscore; on some languages, a prefix is also needed)
Additional problem in Python and VB, among others: || is not an operator. They have "or" for that.
Yeah, I agree.
But I decided to leave that alone, as when I came up with/bb|(?!bb)/ I saw that it was too trivial to be as fun (since it would actually match anything).
Phone lines are never insecure, so why the Internet? I think it was because a bunch of marketers took over the security message aspect of the Internet. Or, some engineers who are FANTASTIC programmers just happened to select the wrong word from the dictionary and it "stuck".
Actually, you didn't get it. Those FANTASTIC programmers just happened to make a so great network that it even has feelings!
Btw, such intelligent network deserves capitalization.
Even this does not truly erase all information, either, as after so many rewrites a sector will become "bad" and the drive will automatically remap that sector to a fresh one and discontinue writing over the one flagged bad.
I thought that was handled by software... more especifically, filesystem software.
If you really wanted to write random values to every byte in the hard drive shouldn't you go for raw writing?
First, as many mentioned before... how could it "only get worse"? It would just not get as good as possible.
And, anyway, Microsoft decided SP2 should be installable on pirated copies, in case you didn't know yet.
- Write and compile code for 68K asm, ARM etc, for various types of portable devices (much cleaner source than C/C++)
Do you still run it in a virtual machine? If so, you are not compiling for portable devices.
Don't take me wrong; I'm not here to bash Java, I'd just like to clarify you always compile it into JVM bytecodes, not into processor-specific opcodes.
Slashdot Mirror
...I thought I could hear Apple... "Why don't you just Think Different, goddammit!"
Well, I'm hard pressed to think of a language where this IS correct. In C, C++, VB, Pascal/Delphi, Haskell, Python, Ruby (and Perl too, I bet): 2b is neither a valid number ("b" is not a digit unless you use 0xN, $N or other hex notations) nor a valid identifier (variables, constants and function names must start with a letter or an underscore; on some languages, a prefix is also needed) Additional problem in Python and VB, among others: || is not an operator. They have "or" for that.
Yeah, I agree. But I decided to leave that alone, as when I came up with /bb|(?!bb)/ I saw that it was too trivial to be as fun (since it would actually match anything).
Apologies!? You've just violated copyrights! Be proud, you'll be one of the first to meet the weasel.
Though they've been compared, I feel sorry for the oranges.
Not to mention "look out the Linux and re-grep"
First, as many mentioned before... how could it "only get worse"? It would just not get as good as possible. And, anyway, Microsoft decided SP2 should be installable on pirated copies, in case you didn't know yet.
- Write and compile code for 68K asm, ARM etc, for various types of portable devices (much cleaner source than C/C++)
Do you still run it in a virtual machine? If so, you are not compiling for portable devices.
Don't take me wrong; I'm not here to bash Java, I'd just like to clarify you always compile it into JVM bytecodes, not into processor-specific opcodes.