|
|
If you ever manage actual endless recursion on a Linear Bounded Automata (like a computer) you will have solved several undecidable computer science problems and opened up a huge can of worms to boot.
I'd pay for front row seats to that. 
If however, you simply want a stack overflow exception, I can work with that too.
Real programmers use butterflies
|
|
|
|
|
Isn't that what functional languages do? 
Well, not really, since they compile to while loops, but the effect is the same 
|
|
|
|
|
Sander Rossel wrote: Can we put some endless recursion in there too?
As long as it is not an endless discussion...  
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
public void Discuss(bool myOpinion, bool otherOpinion)
{
if (myOpinion == otherOpinion)
{
myOpinion != myOpinion;
}
else
{
otherOpinion = myOpinion;
}
Discuss(myOpinion, otherOpinion);
}
|
|
|
|
|
Agreed, because this system shouldn't waste time before crashing. 
|
|
|
|
|
I just want the crashing code to follow Microsoft guidelines and best practices.
Real programmers use butterflies
|
|
|
|
|
Don't tell me you have started to work for the WinUpdates team...
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Needs some recursion. Too understandable as-is. Maybe call this from within the instantiated threads. Yeah, that's it!
|
|
|
|
|
let's just skip right to Stack::Blow();
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Computers need stress tested every once in a while!
|
|
|
|
|
Just tell your computer "we need to talk"
|
|
|
|
|
Yeah, I talked to him before. He's a slightly higher level of noob playing with devices he has little experience with. I saw the docs he's got and they're just a list of function headers with little explanation, written entirely in Chinese.
He was hell-bent on "creating an instance of the API for each reader". I told him he would have to create a class to talk to the readers himself since there isn't one in the library.
|
|
|
|
|
I admire his tenacity at least.
Punching outside your weight class isn't all bad, when you're learning stuff.
It's hard to justify when you're getting paid though.
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: Punching outside your weight class isn't all bad
That's how you learn, for good and for bad
Wrong is evil and must be defeated. - Jeff Ello
Never stop dreaming - Freddie Kruger
|
|
|
|
|
honey the codewitch wrote: And now I feel like a gave a child a loaded pistol
I don't see what the issue is. It sounds like a problem that will soon sort itself out.
|
|
|
|
|
|
Most excellent!
I may even have found my next SOTW 
|
|
|
|
|
Great ..
BR
|
|
|
|
|
Today, in 1954, the first FORTRAN program ran. They don't say how long it took to write/debug it, maybe started in 1953? I can remember clients who insisted in doing accounting using it. After multiply/divide operations (2*$3.50=$6.999999999999), they added .00001. The good old days of punch cards. Still have a few around here, along with a vacuum tube (valve for those of you on the other side of the pond).
Cheers.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
What is old is new again. Got JQuery-Ui drop even to fire yesterday. Momentus occasion here as I have been fighting it off and on for a few days.
|
|
|
|
|
It was about today, in 1969, when I wrote and ran my first Fortran program. It compiled without errors and ran correctly the first time. It has become my canonical "Hello World" program for every new language I encounter. I now know somewhere around 100 programming languages. I've gotten almost all of them to do the right thing on the first whack, but yes there are a few that didn't. APL was one of the embarrassingly frustrating ones, where the complete program consists of 4 characters (plus carriage return), and I got it wrong on that one.
... so why didn't I just write a 'real' "Hello World" program? Because that is something that started with the "C" language, which hadn't been invented yet. At least, in the universe that I lived in.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
Remember APL as well. Did some simulation with it. The old saying still rings true: You can always tell and APL programmer. But not much.
Lou
I would retire but I never got around to commenting my code.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
People are usually shocked when they find out.
|
|
|
|
|
This electrician joke is so lame. Don’t you have some more current one?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
