|
People keep telling me that 
Geek code v 3.12
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++*
Weapons extension: ma- k++ F+2 X
I use 1TBS
|
|
|
|
|
|
Same here, usually I like to know about trivia, about the votes, trailers...
|
|
|
|
|
And I suppose the NSA needs to know who is looking up movies about people who say bad things about US politicians.
Hell, we're in Europe. Finding someone who's got something good to say about a US politician requires a minor miracle.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
... I can't help wishing that my code looked that tidy.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: I can't help wishing that my code looked that tidy.
Oh, for the days when men were real men, women were real women, and every function had one (and only one) exit!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Daniel Pfeffer wrote: and every function had one (and only one) exit!
Indeed!
The GOTO!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
GOTO as a function exit would be a welcome addition to a system I worked on a while ago. This VB6 monster only had one huge function that did every elephanting thing, with GOTOs that decided which part of it to run.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
GOTO is fine; it does what it says on the tin.
I'll bet half the plankies who go on and on about it also go to rallies and scream "GUNS AREN'T DANGEROUS! PEOPLE ARE DANGEROUS!"
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
You mean it's not normal to leave a function with an exception that lands safely in some (empty!) Pokemon catch block?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
"Normal" as in "typical, usual" - unfortunately, yes.
"Normal" as in "good practice" - Hell, no!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Unfortunately, that's right. Recently I had the honor to work on a web application with such interesting exception handling. Unhandled exceptions 'fortunately' were swept under the rug by the JavaScript front end. What moron decided that this would be the optimal default behavior? At least it gives me yet another valid reason to dislike JavaScript.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
In that case, it's: ON ERROR GOTO
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
GOTO only causes problems if it is misused. That's why some people think everything that could cause trouble must be regulated or removed until every circus clown can write programs. I would prefer the opposite approach. Let's keep the programming languages as powerful as they once were and instead remove the circus clowns until we have only people left who know what they are doing.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Oh, Lord, he thinks I'm serious.
However:
if only causes problems if it is misused.
for only causes problems if it is misused.
public only causes problems if it is misused.
private only causes problems if it is misused.
<insert keyword here>* only causes problems if it is misused.
Misuse of anything causes problems.
Fanatical avoidance of a keyword is a kind of misuse.
* Using `` before < breaks the escape character. **
** Starting a line with an asterisk bullets it, so we need an easy replacement for <small>sup</small>, to allow numbered footnotes.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: Oh, Lord, he thinks I'm serious.
Oh, Lord, he thinks my name is Sheldon and that I don't understand such things.
Mark_Wallace wrote: if only causes problems if it is misused.
for only causes problems if it is misused.
public only causes problems if it is misused.
private only causes problems if it is misused.
<insert keyword here>* only causes problems if it is misused.
Great. All those things must be replaced with something foolproof. If that can't be done, we are going to need some new rules and conventions, along with some code Nazis and nanny tools to enforce them.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
ON ERROR RESUME NEXT ?
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Damn! I remember that one!
Funnily enough, I actually found it useful in a tiny UI-window app that only had to accept typed strings and put them into a structured list that was picked up by something else.
The only errors that ever occurred were duplicate string errors, which resulted in the duplicate string not being added to the list, anyway (the desired behaviour), so I just used the resume next line to skip over them.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Wash your keyboard out with soap! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
It's much too late for that. This calls for either an exorcist or purification by fire!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Now THAT'S dangerous - because it is sof freaking tempting  I have the (legacy, not mine) code disseminated of them and sometimes things go awry without any notice 
Geek code v 3.12
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++*
Weapons extension: ma- k++ F+2 X
I use 1TBS
|
|
|
|
|
CTRL+K, CTRL+D - works for me (in C#, C++ is different)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
"Smile - things could be worse!"
I did
Things got worse
PooperPig - Coming Soon
|
|
|
|
|
But why were you so serious? 
You have just been Sharapova'd.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
