Hi, The rules for retain stack usage in the listener are the same as in colon definitions. You must pop what you push. You cannot leave stuff on the retain stack between input lines. The fact that this used to work was a fluke.
Slava On 18-Mar-07, at 3:01 PM, Eduardo Cavazos wrote: > Slava, > > Since I have the stack-display on by default, I noticed a new > persistent item > on the retain stack: > > [ prompt. listener-hook get call listen ] > > I guess technically it's OK for there to be this object there > during a users > listener session. However, it seemes cleaner for the stacks to be > clear by > default. I guess I can get used to it. :-) But a new user might > wonder, "why > is this object always on the retain stack? What happens if I remove > it?". The > listener will break of course. > > I see that this is happening because of until-quit: > > : until-quit ( quot -- ) > quit-flag get > [ quit-flag off drop ] > [ dup slip until-quit ] if ; inline > > Ed > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Factor-talk mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/factor-talk ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
