🚀 go-pugleaf

In article <5785:Nov1519:19:5390@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>If you have a program with a set of variables that enter a loop at time
>t, and continue to loop in a cycle of length l, then the method outlined
>will run the program in twice the memory at one-third speed minus
>housekeeping, and detect the loop between t and t + l, i.e., during its
>first cycle.

That's fine, Dan. What if the cycle length is several millenia?

It's not hard to write a simple program that uses say, 256-bit
integers which accomplishes that.  Your "solution" is hardly practical.

And here's a quick test for your solution:

int foo(x)
int256 x;
{
  while (x != 1) 
    if (even(x))  x = x / 2;
        else x = x * 3 + 1;       
  return 1;
}

>the worst case it'll still detect the loop eventually, though I don't
>think these theoretical statements matter for the real world.

The real world being defined as your experience alone, is it?

>See, this is what I mean about computer scientists. The computational
>model I work with is realistic---it's just my mental picture of what can
>be coded on lots of real machines. As I said before, it's finite. It has

No need to apologize for your limitations, Dan.







Mike Bolotski          Artificial Intelligence Laboratory, MIT
misha@ai.mit.edu       Cambridge, MA