Re: Memory leak with cursors and data structures

Colin Paul Adams <[email protected]> Thu, 14 Aug 2008 16:49:58 +0100
Newsgroups gmane.comp.lang.eiffel.gobo.devel
Message-ID <[email protected]>
>>>>> "Franck" == Franck Arnaud <[email protected]> writes:

    >> Are you going to remove "from" and "until" as well?

    Franck> it goes without saying.

No it doesn't. What about variant and invariant? Does it go without
saying that you are going to remove invariant? And until might want to
be re-used.

    Franck> INTEGER_INTERVAL.do_all, I'd use recursion, it would help
    Franck> if the compiler recognises it in some way so that the
    Franck> generated code does not use stack space, but it's the only
    Franck> place where you need a slight implementation-level cheat.

If the compiler can implement tail recursion, why can't you?

    Franck> as for loops which are open ended and not index-based, (1
    Franck> |..| Maximum_integer).do_until should be OK, and again if

Not for network servers which implement do forever until shutdown
request.
This might well exceed Maximum_integer.

    Franck> all else fails you can always fallback on recursion but

Oh no you can't!
-- 
Colin Adams
Preston Lancashire

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/