PixyMisa
Persnickety Insect
I see.An algorithm, carried out on any system. Cannot do anything.
So how, exactly, did you post the post that you just posted? I believe that an algorithm may very well have been involved.
Uh, no. No. No. In fact, no. Also, no. In fact, I might go so far as to say no. Some might even say no. Or to put it more succinctly, no.All that happens is that each step is evaluated one by one. Whatever is processing each step does so in complete isolation from the last step.
Are you making a distinction between an instantiation of an algorithm and a representation of an algorithm, or are you just making stuff up?The "algorithm" is not examining anything. It is just sitting there in storage.
Apparently you're just making stuff up.It seems trivially true to me.
Are you telling me that algorithms are not run step by step?
Yes, algorithms are run step by step. No, this in no way means, nor can it in any way mean, that each step is isolated from the others.
No, nor does it need to. But any given step of the algorithm can inspect or modify any other given step of the algorithm.Are you telling me that whan a particular step is evaluated the processor goes and has a look at the whole algorithm just to check what is going on?
Okay, again I have to ask you if you are making a distinction between an instantiation of an algorithm and a representation of an algorithm, or just making stuff up?An algorithm is not a thing that can inspect anything. It is just a bunch of numbers.
No, but if can find out. Using... An algorithm!The CPU does not know what has come before when it processees an instruction.
No, but it doesn't need to. On any Turing-complete system, the algorithm can examine and modify its own steps.But the data that the processor is processing at any particular time does not have all of that logic encoded into it.
Not to put too fine a point on it, wrong. The step can see whatever it is that the algorithm requires the step to see, assuming that the things it is supposed to see can be expressed algorithmically. This includes the previous step of the algorithm. Or the subsequent step. Or any other step.If I add 4+2 and get 6, by the time the next instruction comes along the "4+2" cannot be deduced from the 6. The step sees 6 and nothing else.
Are you making a distinction... I expect you know the drill by now.Because algorithms can't do things.
Yes, they can be expressed that way. See Godel's Incompleteness Theorem for what you can do with a bunch of numbers.They are a bunch of numbers, that is all.
Certainly.They are processed step by step.
And since the algorithm itself can be expressed as a bunch of numbers, the algorithm can examine and modify itself.One step at a time, the only information that the processor considers is the particular numbers it needs to process.
Yes. Yes it is. That is what it is. An algorithm is what it is. What it is is an algorithm.If you are describing something that can inspect itself or do anything whatsoever you are not describing an algorithm.
Go back to the Church-Turing thesis for a moment. Any algorithm can be implemented on a Turing Machine. And anything that can be implemented on a Turing Machine is an algorithm. A Turing Machine can modify its own operation. Therefore...
Are you making a distinction, et cetera, et cetera...An algorithm does not do anything.
Of course they do, Robin! Look at the definition of algorithm and the mechanism of the Turing Machine.I mean for crying out loud - cyborg says algorithms have nothing to do with numbers, and you and PixyMisa tell me they are things with some internal power to inspect themselves.