[Pharo-project] Infinite recursion

Guillermo Polito guillermopolito at gmail.com
Fri Nov 19 13:29:59 CET 2010

I will insist here :P.

What is the desired behavior for this situation?  So if it is an Issue, I
may open an entry in the tracker...

On Wed, Nov 17, 2010 at 1:46 PM, Schwab,Wilhelm K <bschwab at anest.ufl.edu>wrote:

> I asked this some time back.  One dark side of doing this is that it *can*
> result in unwanted/inappropriate failures.  In practice though, Dolphin's
> limits on the stack has been a good thing.
> ________________________________________
> From: pharo-project-bounces at lists.gforge.inria.fr [
> pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Guillermo Polito
> [guillermopolito at gmail.com]
> Sent: Wednesday, November 17, 2010 11:44 AM
> To: Pharo-project at lists.gforge.inria.fr
> Subject: [Pharo-project] Infinite recursion
> Hi,
> Yesterday I got into an infinite recursion, because of adding an ordered
> collection into itself.  And #hash is defined in terms of its containees,
> hehe.
> Why I did that? It doesn't really matters. I was testing a little project
> I'm doing for the University.
> So I came into an infinite recursion, which didn't stop until the VM run
> out of memory...  And the question is.. Shouldn't it throw an error like a
> stack overflow when we run into those cases?
> Cheers,
> Guille
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20101119/beae3cf4/attachment.htm>

More information about the Pharo-project mailing list