|
Random answer of the week - Nope
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
I thought not, wait if the answer was random does that mean it could really be yep, or maybe.
|
|
|
|
|
That's not how you spell QA
This space for rent
|
|
|
|
|
"QWIK ANSERZ"
Fits perfectly!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Eh ?
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
"Leave after finding nothing in big rambling empty space" is a perfect description for quick answers.
This space for rent
|
|
|
|
|
Gobi Desert.
Big, rambling -> Gbi
Find nothing (o) in it -> Gobi
Leave after -> desert.
Andy B
|
|
|
|
|
Yay well done
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
|
And he didn't even get to the "white-list us on your ad-blocker" blocker ...
98.4% of statistics are made up on the spot.
|
|
|
|
|
Or the "FarceBok Like" page...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Tried it at the weekend to read about a fatal RTC that happened a few doors down from me. Without an ad-blocker, that description is fairly accurate.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
|
It has in the past, but not anymore?
|
|
|
|
|
So you finally have arrived at JavaScript?
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
It did me. Made me much better at chess.
|
|
|
|
|
Very serious article
Quote: The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offence
|
|
|
|
|
Real Life Imitates Art!
My going to your link perfectly aligns with The Lounge[^]
Also - if one really want to - they can "view source' and read it without any deco.
They'll get me to disable my ad-blocker when they unwrap my cold dead . . . oops, wrong forum.
[EDIT]
"5 Lessons to Become a Really Good Self-Taught Programmer" is brought up near the end - a really ironic statement. Lessons for people who don't take lessons!
[/EDIT]
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
modified 1-May-18 7:58am.
|
|
|
|
|
Alzheimer's gets a little bit in the way of programming, that is why programmers don't get Alzheimer's. It's like saying professional hockey players are less likely to get a heart attack.
throughout my life, my two greatest assets have been mental stability and being, like, really smart.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
Hockey players have fewer cavities.
|
|
|
|
|
Looks like the bug is gonna be crushed soon!
it only took me 3 days (So far...), one of my longest (C# bug) chase...
And it's in C#...
I have pinpointed it completely yet, so I dunno why Visual Studio was not breaking on the exception yet.. But getting there, only a few hundreds of line of possible cause...
[EDIT]
Nailed it!
The evilest code that can be! Visual Studio will absolutely not help you find what was wrong here!!
The Weird and The Wonderful
modified 30-Apr-18 23:40pm.
|
|
|
|
|
You can't trust debuggers.
|
|
|
|
|
They are generally helpful though!
|
|
|
|
|
Sorry to spoil your fun, but ... it's been that way for a long time, and it's a "feature" not a "bug".I.e. it's in the documentation: StackOverflowException Class (System)[^]
MSDN (Remarks): In the .NET Framework 1.0 and 1.1, you could catch a StackOverflowException object (for example, to recover from unbounded recursion). Starting with the .NET Framework 2.0, you can’t catch a StackOverflowException object with a try/catch block, and the corresponding process is terminated by default. Consequently, you should write your code to detect and prevent a stack overflow. For example, if your app depends on recursion, use a counter or a state condition to terminate the recursive loop.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Yeah, I was vaguely aware of that. It's one of those funny exceptions like ThreadAbortException and the stuff of body bags.
It's not immediately obvious to me though why it cannot be caught, perhaps to do with the limits on the stack trace/unwindability? Particularly in the managed world you'd think it could be handled gracefully. But then, is the stack checked by the CLR (surely) or does this rely on some more fundamental interrupt based or other such approach? Using a counter to detect recursive level is filthy.
I demand answers.
Regards,
Rob Philpott.
|
|
|
|