quentron.com

[sarkeizen]

To argue with a looser that does not understand his own code, is totally a waste of my time.

Actually, I misread...you actually have written a different program.  It still doesn't work.

WillThisEnd(WillThisEndOnSelf(WillThisEndOnSelf)))

(I assumed the extra use of "program" was an error because it means you've written something rather different than what I wrote.  Since you've refused to learn proper C syntax and like a huge douche refuse to answer questions about your code properly I'm forced to make guesses like this)

So what you wrote will call the inner function first  WillThisEndOnSelf with a parameter of WillThisEndOnSelf.  It in turn calls WillThisEnd(WillThisEndOnSelf,WillThisEndOnSelf).  In which case WillThisEndOnSelf() will either terminate or go into an infinite loop - whatever is the opposite of WillThisEnd's prediction.   So it still fails horribly there.

If it does exit it returns an undefined value (there is no return value for WillThisEndOnSelf - so assuming you could get this to compile you would get garbage).  You would then call WillThisEnd(<some garbage pointer>)

Who's the loser here?  The guy who can't write C.  Perhaps if you told me what you WANT to write.  I can give you a hand.  Perhaps point you to some beginner pages?

Bruce_TPU - more colouring fun for you!

[Regster]

Actually, I misread...you actually have written a different program.  It still doesn't work.

WillThisEnd(WillThisEndOnSelf(WillThisEndOnSelf)))

(I assumed the extra use of "program" was an error because it means you've written something rather different than what I wrote.  Since you've refused to learn proper C syntax and like a huge douche refuse to answer questions about your code properly I'm forced to make guesses like this)

So what you wrote will call the inner function first  WillThisEndOnSelf with a parameter of WillThisEndOnSelf.  It in turn calls WillThisEnd(WillThisEndOnSelf,WillThisEndOnSelf).  In which case WillThisEndOnSelf() will either terminate or go into an infinite loop - whatever is the opposite of WillThisEnd's prediction.   So it still fails horribly there.

If it does exit it returns an undefined value (there is no return value for WillThisEndOnSelf - so assuming you could get this to compile you would get garbage).  You would then call WillThisEnd(<some garbage pointer>)

Who's the loser here?  The guy who can't write C.  Perhaps if you told me what you WANT to write.  I can give you a hand.  Perhaps point you to some beginner pages?

Bruce_TPU - more colouring fun for you!

It's perfectly possible to parse a few lines of code to check for some infinite loop.  If you are talking about large programs, then it is perfectly possible to parse a few more lines of code to check for some infinite loop.  If it's possible for one, then it is possible for the other.

Are you a web developer?

[lumen]

Actually, I misread...you actually have written a different program.  It still doesn't work.

WillThisEnd(WillThisEndOnSelf(WillThisEndOnSelf)))

(I assumed the extra use of "program" was an error because it means you've written something rather different than what I wrote.  Since you've refused to learn proper C syntax and like a huge douche refuse to answer questions about your code properly I'm forced to make guesses like this)

So what you wrote will call the inner function first  WillThisEndOnSelf with a parameter of WillThisEndOnSelf.  It in turn calls WillThisEnd(WillThisEndOnSelf,WillThisEndOnSelf).  In which case WillThisEndOnSelf() will either terminate or go into an infinite loop - whatever is the opposite of WillThisEnd's prediction.   So it still fails horribly there.

If it does exit it returns an undefined value (there is no return value for WillThisEndOnSelf - so assuming you could get this to compile you would get garbage).  You would then call WillThisEnd(<some garbage pointer>)

Who's the loser here?  The guy who can't write C.  Perhaps if you told me what you WANT to write.  I can give you a hand.  Perhaps point you to some beginner pages?

Bruce_TPU - more colouring fun for you!

Your claim:

"That is it doesn't ALWAYS, predict the correct answer."

"whatever is the opposite of WillThisEnd's prediction."


I will just give you the one part of your code that YOU do not understand.


"WillThisEnd()" does not make a prediction.
"WillThisEnd()" returns it's result after it has finished running.
You think you are fooling the program "WillThisEnd()" by using it's results, but it has already finished.

Again, you are looking out of the scope of the function.
But it is your story, so whatever you say.

You see everyone is a welder, but not everyone can weld.

[Regster]

What we are looking at with quenco is, essentially, a salmon leap for electrons.  There is no need for external intelligence in the process of fish of greater or lesser strength jumping up (or not) a leap.

I'm enjoying the programming jibber jabber though.  Let's talk about C some more.

[sarkeizen]

It's perfectly possible to parse a few lines of code to check for some infinite loop.  If you are talking about large programs, then it is perfectly possible to parse a few more lines of code to check for some infinite loop.  If it's possible for one, then it is possible for the other.

You can check for some specific cases sure, or some restricted environments but you can not determinstically check for all cases.

Are you a web developer?

Is that supposed to be an insult?