Michael Ulm wrote:
> John W. Long wrote:
> 
>> List Recv wrote:
>>
>>> Okay, Ruby core hackers, can you answer our call?!
>>
>>
>> I don't think there's a need for Ruby core hacking if you follow my
>> suggestion:
>>
>>  >> One thing you could do would be to load up all of your libraries and
>>  >> pause on the terminal waiting for user input. As soon as the user
>>  >> unpaused the process it would load in the test cases and run them. As
>>  >> the user was looking at the output and fixing tests you could load up
>>  >> another instance and pause waiting for user input. Stir and repeat...
>>
> 
> That would work in this one case where resetting is useful. As this
> thread has shown, there are others. Here is mine: I want to use an
> irb-like environment in conjunction with gsl as a kind of super
> calculator/numerical test engine. A reset method would be tremendously
> useful as one often wants to start with a clean slate, without losing
> all the output from the previous computations.
> 
> So, I second List Recv's plea to the core hackers: ideas anyone?
> 

Doesn't GC clean the slate well enough for calculations?

-- 
      vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407