David Megginson <[EMAIL PROTECTED]> said:

> Norman Vine writes:
> 
>  > So ???
> 
> So it hurts development a lot.  Developers have limited time to
> contribute to FlightGear, and if the program takes always takes 5 or
> 10 minutes to rebuild (and has to be rebuilt, say, 10 times to test
> and debug each change), we all suffer because a lot less code gets
> written and debugged.
> 
> There's an easy solution here -- remove FGGlobals::get_current_view
> completely and have the callers use FGGlobals::get_view_mgr to get the
> current view.  The right solution, though, is to find out *why* so
> many parts of the code are using this method.
> 
 
That won't help, these calls are for the class pointer.  I'd really like it 
if you guys just ignored this one until about a week from now. :-)

It takes 20 minutes or close to it for me to do a rebuild sometimes,  but it
is only when changing headers, which usually doesn't happen all that much. 
Generally when I have to add something to a popular class, I try and organize
what I'm doing around the inevitable rebuild.  And then I remind myself of the
days when this little communication program I wrote in 6502 assembler took 11
hours to build :-).  In those days you worked harder to avoid bugs.  And that
was a good thing.

So anyway, I think it is fine the way it is.  There are far too many classes
accessing the viewer for info that should be held elsewhere, and soon it'll be
much better.

Best,

Jim

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to