Quoting Melchior FRANZ : > * Frederic Bouvier -- Tuesday 18 April 2006 23:13: > > What about applying the simple patch attached. It doesn't cure the > > double entries problem, but it ensures that no valid memory is returned > > to the system before all references on it are released. > > Almost everything is better than crashes, but in this case it would > mean that we throw band-aid at a problem, because we consider it > unfixable or not worth to be fixed. Why should a "holding pattern" > list and a "runway" list be allowed to *share* an aircraft? The > aircraft can only be in one state, if the code does its job. I find > this a disgusting "fix". But then again, almost everything is better > than crashes ... :-]
So why not using a single list and a state variable in the plane record ? BTW: I don't think using a smart memory management technique should be ignored just because this particular problem is fixed ( in a near future I hope ). -Fred -- Frédéric Bouvier http://frfoto.free.fr Photo gallery - album photo http://www.fotolia.fr/p/2278 Other photo gallery http://fgsd.sourceforge.net/ FlightGear Scenery Designer ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
