Another problem!!

[Warrior]

x86] link=topic=7608.msg96665#msg96665 date=1162150206]
Funny you get mad over something on the internet, oh well. There is just no way I'm wrong, my proof is in the word itself. I'm fully aware when you say loop isn't just limited to recursion but the point is that, it includes recursion.

Ugh why am I even continuing this with you, I don't care. If you want to defy a definition to prove that you win then so be it, I'll just get on with my life.

You obsess too much over these things imho.

It doesn't matter where I encounter them, idiots always piss me off.

I'm not defying the definition.  Like I said, you're abstracting the definition of a loop and using the abstracted definition to relate it to recursion.  I'm not saying that recursion isn't looping; however, it isn't a loop when you use the definition of the word "loop" in the context of a programming language.

What the hell are you talking about? A loop is simply reusing the same code over and over... I'm not abstracting the definition that is exactly what infinite recursion is, an infinite loop.

Just out of curiosity, what do you definite infinite recursion as?

[Sidoh]

x86] link=topic=7608.msg96667#msg96667 date=1162150883]
What the hell are you talking about? A loop is simply reusing the same code over and over... I'm not abstracting the definition that is exactly what infinite recursion is, an infinite loop.

Yes, that is the abstracted definition of a loop in programming.  The applied meaning of a loop is (as MyndFyre already explained quite plainly):

Code Select Expand

while(condition) { statement; }

Code Select Expand

for(initializer; condition; update) { statement; }

That is a programming loop.

x86] link=topic=7608.msg96667#msg96667 date=1162150883]
Just out of curiosity, what do you definite infinite recursion as?

Code Select Expand

function statement(a) { statement(a++); }

[Warrior]

x86] link=topic=7608.msg96667#msg96667 date=1162150883]
What the hell are you talking about? A loop is simply reusing the same code over and over... I'm not abstracting the definition that is exactly what infinite recursion is, an infinite loop.

Yes, that is the abstracted definition of a loop in programming.  The applied meaning of a loop is (as MyndFyre already explained quite plainly):

Code Select Expand

while(condition) { statement; }

Code Select Expand

for(initializer; condition; update) { statement; }

That is a programming loop.

x86] link=topic=7608.msg96667#msg96667 date=1162150883]
Just out of curiosity, what do you definite infinite recursion as?

Code Select Expand

function statement(a) { statement(a++); }

Those are two different types of loops, you're just limiting what the term loop applies to as it fits your needs.

The bottom line is that infinite recursions are infinite loops are infinite loops are infinite loops.

No way around it, no way to argue against it.

[Sidoh]

x86] link=topic=7608.msg96672#msg96672 date=1162151961]
Those are two different types of loops, you're just limiting what the term loop applies to as it fits your needs.

The bottom line is that infinite recursions are infinite loops are infinite loops are infinite loops.

No way around it, no way to argue against it.

First, I think you need to understand the definition of abstract:

abstract: 1 a : disassociated from any specific instance <an abstract entity>

Next, I'll quote some definitions of recursion, most of which are from your own source.

Recursion in computer programming is exemplified when a function is defined in terms of itself. One example application of recursion is in parsers for programming languages. The great advantage of recursion is that an infinite set of possible sentences, designs or other data can be defined, parsed or produced by a finite computer program.

Recursion is the definition of an operation in terms of itself.

Recursion programming technique in which a program or routine calls itself to perform successive steps in an operation, with each step using the output of the preceding step.

Nowadays, only the most performance-hungry software, such as video games, missile guidance systems and graphics card drivers, should worry about whether recursion will be slower than iterative for or while loops.

Notice that they refer to recursion and the types of programming loops as separate entities in the last quote.

Do you recognize the difference yet?

[Warrior]

ok your point? Recursion = Looping. Infinite recursion = Infinite looping.

Still, I win.

[Sidoh]

x86] link=topic=7608.msg96676#msg96676 date=1162153431]
Recursion = Looping.

That's where you're wrong.  Looping is not recursion.  Did you even read those definitions?  You're a programmer, right?

Are you making an effort to ignore everything that's thrown at you or does that come naturally?

[iago]

Ok, let's pretend that you can make an infinite loop without a loop.  Just for a minute. 

Now, if you infinitely recurse, you run out of stack space (you get to the top.. or the bottom, depending on how you look at it).  Then your program crashes, since it can't write anything else to the stack. 

So where's this corruption you're talking about?

[Warrior]

Ok, let's pretend that you can make an infinite loop without a loop.  Just for a minute. 

Now, if you infinitely recurse, you run out of stack space (you get to the top.. or the bottom, depending on how you look at it).  Then your program crashes, since it can't write anything else to the stack. 

So where's this corruption you're talking about?

It is obviously corrupted if it's crashed right? I mean..the program wouldn't crash if it wasn't corrupted.

[iago]

x86] link=topic=7608.msg96689#msg96689 date=1162161773]

Ok, let's pretend that you can make an infinite loop without a loop.  Just for a minute. 

Now, if you infinitely recurse, you run out of stack space (you get to the top.. or the bottom, depending on how you look at it).  Then your program crashes, since it can't write anything else to the stack. 

So where's this corruption you're talking about?

It is obviously corrupted if it's crashed right? I mean..the program wouldn't crash if it wasn't corrupted.

No.  As I said, it crashes because it's out of stack space, not because it's corrupted. 

[MyndFyre]

Warrior, I can't believe nobody has pointed this out.  Recursion is in fact a looping construction.  However, loops are not always recursive.

It's like this:

Set(Programming constructs) = { Loops, Assignments, Expressions, Functions }
Set(Loops) = (Recursive loops, While loops, For loops, Do loops }

Or, if you want to think of it this way:

Code Select Expand


class Loop : ProgrammingIdea
{
...
}

Class Recursion : Loop
{
...
}

You can implicitly cast a Recursion object to a Loop object.  However, you cannot safely cast a Loop object to a Recursion object.

[Joe]

x86] link=topic=7608.msg96574#msg96574 date=1162074606]

x86] link=topic=7608.msg96557#msg96557 date=1162063604]
Second of all, infinite looping != infinite recursion.

Infinite recursion, a special case of an infinite loop, is an infinite loop caused by recursion.

My God, Warrior... Even I know that simply increasing an integer has absolutely nothing to do with the stack! Pushing it, calling a function, and popping it, however, does!

[Warrior]

x86] link=topic=7608.msg96745#msg96745 date=1162213321]

x86] link=topic=7608.msg96574#msg96574 date=1162074606]

x86] link=topic=7608.msg96557#msg96557 date=1162063604]
Second of all, infinite looping != infinite recursion.

Infinite recursion, a special case of an infinite loop, is an infinite loop caused by recursion.

My God, Warrior... Even I know that simply increasing an integer has absolutely nothing to do with the stack! Pushing it, calling a function, and popping it, however, does!

Joe:
I just saw this today. You have no idea what you're talking about, read it the entire thread tool.
Bottom line: I program better than you.

@Myndfyre: Yea, you're right. I admit defeat.