On 03/01/2007 02:19 PM, AJ MacLeod wrote: > This patch promises to > address quite a few niggles that I've noticed over the past few years, thanks > for working on it...
:-) Having a usable ATIS is important, if you're interested in realism. > Was the stuff at line 300 intended to be in there? Actually yes, I put the call-trace in there for a reason, and I left it in there for a reason. I thought that in the future, some folks might find it helpful to see how/where this code was being called. -- Obviously I don't benefit directly from these comments. I know what calls what. If I didn't a couple days ago, I sure do now. -- Obviously there are some other people on this list who won't benefit directly, either. They already know what calls what. ++ However ... there is a theory going around that says the project benefits -- i.e. the community as a whole benefits -- if open code is really, really open in a broad /practical/ sense (not just in a narrow legal sense). That includes making it practical for lots of folks -- not just me and a handful of others -- to understand the code and make further improvements on it. I can explain more about this if anyone is interested. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
