Robert <dogg...@googlemail.com> writes: > In the case of nasal, I believe the garbage collection pass must > be done in a single atomic step, otherwise it would leave the heap > in an inconsistent state and adversely affect the scripts. > > I completely agree with you. Now I understand the whole thing much > better. I originally thought about a non-mutual-exclusive thread ( > completely asynchronous ), but then it would potentially leave a mess > in Nasal heap, right? > > It might be possible to use a GC module from a GPL:d Java vm or > similar. > > That's a good idea. As Curtis Olson said the GC should have an atomic > step character (or don't produce too much delay). > > Does anybody of you know how garbage collectors of Java and Python and > other GPL'd script engines compare to each other? (atomic step > character)
Google gives lot of real-time and multi-threaded real-time garbage collection algorithms. I don't know which is best. -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}. ------------------------------------------------------------------------------ Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
