On Wed, 6 Apr 2005 [EMAIL PROTECTED] wrote:
Why the internal hard limit? If people want to use up all their memory, that's their problem. A warning in the docs is good, but just giving up at an arbitrary number just makes the software less useful.
I think this can be fixed - I'll try and make some tests.
One possibility is to simply return undef for methods that might cause infinite loops when we don't know for certain they won't.
Calculating whether or not this can happen is probably possible in some cases (defined start & end), and in others we can offer a constructor flag.
-dave
/*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/
