Hi Phil, This should be documented but it is not a bug. The optimizer is very aggressive and you should not write code that relies on the entire stack contents.
On Wed, Sep 10, 2008 at 6:30 AM, Phil Dawes <[EMAIL PROTECTED]> wrote: > Hi Slava, Hi Factor list, > > This just caught me out: > > The optimizer prunes unused values even if there's code to inspect the > stack. So e.g. > > ( scratchpad ) USE: compiler.tree.debugger > ( scratchpad ) [ 35 .s drop ] optimized. > [ .s ] > > i.e. you wouldn't see '35' when .s prints the stack in compiled code. > > I'm not sure whether this should be considered a bug, but it caused me a > bit of headscratching when trying to debug some web code. (the web code > was outputting the stack contents to the browser, but the values in the > stack got optimized out!). > > Cheers, > > Phil > > > > ------------------------------------------------------------------------- > 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=/ > _______________________________________________ > Factor-talk mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/factor-talk > ------------------------------------------------------------------------- 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=/ _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
