Visual bloody bollocks basic.
Aug. 14th, 2008 06:52 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
sobriqueToday has been VBS day.
Been a bit grumpy, as when I'm concentrating on code, when I say "just a minute" that means – I acknowledge you want attention, but I’'m right in the middle of thinking about something, and will lose my train of thought if I stop right now, so please stand by.
Not "carry on talking at me, and asking me to respond meaningfully when I’m concentrating".
However this annoyance pails into insignificance:
"On Error Resume Next"
I’m modifying some code.
I have found some MONKEY has put this in, and … well, hadn't given it much thought.
It’s a great VBS hack. What it means, is if you right crap code, then the program should just BODGE ON ANYWAY.
Yeah. So … if I typo in my loop, such that it’s a runtime error (like for example, using "sleep(60000) rather than "wscript.sleep 60000") it just … skips that loop, and carrys on, neatly jumping over my "while" loops, singing "lalalaalala, no you don’t want to do that bit, I'll ignore it".
Which moron, designed a programming langage where this was EVEN POSSIBLE.
It is acceptable to have runtime errors, not crashing a program. It is acceptable when I write some error handling code, that explicitly defines the behaviour when I do this. So I can … try running a command, and if it’s not there _do something else, defined_ not just arbitrarily continue and pretend it never happened.
GAAH.
Been a bit grumpy, as when I'm concentrating on code, when I say "just a minute" that means – I acknowledge you want attention, but I’'m right in the middle of thinking about something, and will lose my train of thought if I stop right now, so please stand by.
Not "carry on talking at me, and asking me to respond meaningfully when I’m concentrating".
However this annoyance pails into insignificance:
"On Error Resume Next"
I’m modifying some code.
I have found some MONKEY has put this in, and … well, hadn't given it much thought.
It’s a great VBS hack. What it means, is if you right crap code, then the program should just BODGE ON ANYWAY.
Yeah. So … if I typo in my loop, such that it’s a runtime error (like for example, using "sleep(60000) rather than "wscript.sleep 60000") it just … skips that loop, and carrys on, neatly jumping over my "while" loops, singing "lalalaalala, no you don’t want to do that bit, I'll ignore it".
Which moron, designed a programming langage where this was EVEN POSSIBLE.
It is acceptable to have runtime errors, not crashing a program. It is acceptable when I write some error handling code, that explicitly defines the behaviour when I do this. So I can … try running a command, and if it’s not there _do something else, defined_ not just arbitrarily continue and pretend it never happened.
GAAH.
