On 19 Dec 2009, at 19:03, Vivian Meazza wrote: > Hey guys, don't we test code/scripts nowadays before stuffing it into CVS?
Well the C++ code works - for this kind of thing I was lazy and hoped the person who requested the feature will test it and let me know if they encounter problems. I also figured such a simple change would be obviously correct, even though what I managed was the exact opposite :) About to head out for food now, so I'll fix the name in the morning - suggestions still welcome on what to call it! In terms of testing, I know the glideslope tunnel uses airportinfo(), but that's the only use I'm aware of in CVS - so what *is* the best way to test this, from a script? The person requesting the feature is working on code outside CVS, as I understand it. Regards, James ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
