It happened to me more than once, that I accidently had some huge objects hanging in a workspace leading to a memory leak. So remembering the variables can be a dangerous thing.
However, just remembering the string isn't that useful either. I often build objects that I keep around in a workspace to play with. Without remembering these instances the code snippets in the workspace are useless. So I don't know ;-) Lukas On Tue, Jan 20, 2009 at 8:46 AM, Stéphane Ducasse <stephane.duca...@inria.fr> wrote: > I would not bother there are inspectors for this kind of things. > You create an object and get several snippets > > Else you write a class, no? > > > On Jan 19, 2009, at 11:23 PM, Alexandre Bergel wrote: > >>> Neat behaviour - I'll have to try it out (like, what happens when >>> you have 5 open workspaces - do they all have access to the same >>> list of history? Just something to try). >>> >>> What about contents of workspace variables? Are those stored in the >>> history as well? >> >> Actually, I seldom reuse variables across workspaces and have no more >> than 2 or 3 workspace at the same time. >> What would be the ideal scenario for variables? >> >> Thanks for your words, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project@lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
