quentron.com

[lumen]

What is "it" in this sentence.  You used it six times.

Please replace it with either WillThisEnd() or WillThisEndOnSelf() where applicable.

So now, you already know you lost and at this point hope that I make some mistake so you can carry on. How cool is that!

WillThisEnd(WillThisEndOnSelf(WillThisEnd) )



If WillThisEnd() finds WillThisEndOnSelf() is indeed itself, WillThisEnd() does not run WillThisEndOnSelf(), WillThisEnd() simply returns TRUE, because WillThisEnd() already knows that WillThisEndOnSelf() ends.

Why are you still bothering, your king is down!

[sarkeizen]

So now, you already know you lost and at this point hope that I make some mistake so you can carry on. How cool is that!

I think I've complained about you being vague enough to make it unsurprising that occasionally you'll cross the line from vague to illucid.  In this case you started a post with "it" and then continued to reference "it" (at least seven times) but didn't define what the term was referencing.  Perhaps this only happens when you're excited.

If WillThisEnd() finds WillThisEndOnSelf() is indeed itself

English parsing rules still consider this sentence ambiguous.   Is "itself" WillThisEnd() or WillThisEndOnSelf().

Why are you still bothering, your king is down!

Perhaps you better make a clearer argument before you start jacking yourself off.  So far you might as well typed:  "it that it which it is part of it and that other it in it"

Also...

WillThisEnd(WillThisEndOnSelf(WillThisEnd) )

This isn't the code that's causing the problem.  Altering my program to make your broken interpreter work properly doesn't solve the halting problem.  Not to mention the way you've written this you should see an exception or it shouldn't compile.

[orbut 3000]

willThisEnd(thisThread) may return 'true' soon. 

[Bruce_TPU]

@ Lumen,

Trying to talk to Sarkey is USELESS.  Please, for the love of sanity, ignore his sensless drivel and diatribes.
It is WORST then hitting ones head upon a brick wall.

Cheers,

Bruce

[lumen]

I think I've complained about you being vague enough to make it unsurprising that occasionally you'll cross the line from vague to illucid.  In this case you started a post with "it" and then continued to reference "it" (at least seven times) but didn't define what the term was referencing.  Perhaps this only happens when you're excited.English parsing rules still consider this sentence ambiguous.   Is "itself" WillThisEnd() or WillThisEndOnSelf().Perhaps you better make a clearer argument before you start jacking yourself off.  So far you might as well typed:  "it that it which it is part of it and that other it in it"

Also...This isn't the code that's causing the problem.  Altering my program to make your broken interpreter work properly doesn't solve the halting problem.  Not to mention the way you've written this you should see an exception or it shouldn't compile.

Oh, but how the arguments are not correct, Oh, It might not even compile, Oh...... Oh.

Your just trying to put the proof on me to show it works. Let me just give you the one line that fixes the entire error you keep seeing.

WillThisEnd(WillThisEnd) = True

WillThisEnd can run itself, and produce a TRUE (yes this program will finish).

This WAS the only case that it could not run, so excluding this single case and providing the correct result DOES SOLVE THE ENTIRE PROBLEM.

Sorry, you have now learned a valuable lesson.
Don't ever think you know more than anyone else.
There is always someone that knows more or is faster or is stronger or is better looking. If it's not me, it's someone else.

I tire of this game and I have real work to do today. We can play another game again soon.