Re: [Flightgear-devel] FlightGear Make Process: Amazing

2006-02-28 Thread Ampere K. Hardraade
On Tuesday 28 February 2006 12:04, David Megginson wrote: > Yes, sadly.  If big companies are going to waste that much money, I > wish they'd waste some more of it in people like us. > > > All the best, > > > David We might get money thrown at us if we somehow tie AJAX into the project. ;-) Amper

Re: [Flightgear-devel] FlightGear Make Process: Amazing

2006-02-28 Thread David Megginson
On 28/02/06, Jim Wilson <[EMAIL PROTECTED]> wrote: > I knew it! Time for another rate increase. The big consulting companies get that money, then hire inexperienced, underpaid programmers to do the work. > Tell me the price of those projects at least included some test hardware, > documentatio

Re: [Flightgear-devel] FlightGear Make Process: Amazing

2006-02-27 Thread Jim Wilson
> From: "David Megginson" > > On 27/02/06, Curtis L. Olson <[EMAIL PROTECTED]> wrote: > > > If you dig up a utility called "sloc" (source lines of code) it suggests > > that we are sitting on a body of code that would have cost 10's of > > millions of dollars to produce had we done it in a tradit

Re: [Flightgear-devel] FlightGear Make Process: Amazing

2006-02-27 Thread Ampere K. Hardraade
On Monday 27 February 2006 10:50, David Megginson wrote: > Why stop there, though?  The base package contains about 95,000 (!!!) > lines of XML and nearly 30,000 lines of NASAL scripts.  Of course, we > should also count the raster graphics, sound samples, 3D models, > non-XML data files, etc. etc.

Re: [Flightgear-devel] FlightGear Make Process: Amazing

2006-02-27 Thread David Megginson
On 27/02/06, Curtis L. Olson <[EMAIL PROTECTED]> wrote: > If you dig up a utility called "sloc" (source lines of code) it suggests > that we are sitting on a body of code that would have cost 10's of > millions of dollars to produce had we done it in a traditional > commercial environment. It mak

Re: [Flightgear-devel] FlightGear Make Process: Amazing

2006-02-27 Thread Curtis L. Olson
David Megginson wrote: It's not all that useful a metric -- I'd prefer to count methods, functions, etc. -- but FlightGear checks in at roughly 215,000 lines of C/C++ code, and SimGear checks in at close to 75,000 lines. Why stop there, though? The base package contains about 95,000 (!!!) line

Re: [Flightgear-devel] FlightGear Make Process: Amazing

2006-02-27 Thread Durk Talsma
On Monday 27 February 2006 16:50, David Megginson wrote: > On 27/02/06, Jon S. Berndt <[EMAIL PROTECTED]> wrote: > > Has anyone ever checked to see how many lines of code are involved in > > plib/simgear/flightgear? > > It's not all that useful a metric -- I'd prefer to count methods, > functions,

RE: [Flightgear-devel] FlightGear Make Process: Amazing

2006-02-27 Thread Jon S. Berndt
> Another metric: there are ~1500 files > in the plib/simgear/flightgear codebase. > > Jon Here's a clarification (before I get called on this), there are ~1500 .c, .h, .cpp, .cxx, and .hxx files. Jon --- This SF.Net email is sponsored by xP

RE: [Flightgear-devel] FlightGear Make Process: Amazing

2006-02-27 Thread Jon S. Berndt
> It's not all that useful a metric -- I'd prefer to count methods, > functions, etc. -- but FlightGear checks in at roughly 215,000 lines > of C/C++ code, and SimGear checks in at close to 75,000 lines. > > Why stop there, though? The base package contains about 95,000 (!!!) > lines of XML and ne

RE: [Flightgear-devel] FlightGear Make Process: Amazing

2006-02-27 Thread Jon S. Berndt
> Has anyone ever checked to see how many lines of code are involved in > plib/simgear/flightgear? > > Jon This: wc `find . -name "*.[ch]??";find . -name "*.[ch]"` results in a finding that there are 420,000+ lines in the source and header files. That's not lines-of-code, but just lines. Jon

Re: [Flightgear-devel] FlightGear Make Process: Amazing

2006-02-27 Thread David Megginson
On 27/02/06, Jon S. Berndt <[EMAIL PROTECTED]> wrote: > Has anyone ever checked to see how many lines of code are involved in > plib/simgear/flightgear? It's not all that useful a metric -- I'd prefer to count methods, functions, etc. -- but FlightGear checks in at roughly 215,000 lines of C/C++