On Wednesday, April 17, 2002, at 07:45 PM, Julian Foad wrote:
> Jonathan Polley wrote:
>>
>> My C training goes back to circa 1985, at which time all floats were
>> passed as doubles.
>
> Yes, they were.
>
>> In fact, the modern C/C++ compilers to which I have
>> access still do this (I don't u
Jonathan Polley wrote:
>
> My C training goes back to circa 1985, at which time all floats were
> passed as doubles.
Yes, they were.
> In fact, the modern C/C++ compilers to which I have
> access still do this (I don't use gcc, except to rebuild FlightGear).
Oh? Which compilers?
> All
> fl
Jonathan Polley writes:
>
>I must be older than anyone else here, but my collegiate C
>training
Nah, If you had 'C' courses in college you are just a 'pup' :-)
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.or
On Tuesday, April 16, 2002, at 11:54 PM, Julian Foad wrote:
> Jonathan Polley wrote:
>>
> ...
>>
>> Aside from removing unreferenced variables, the bulk of the changes were
>> in the area of the use of floating-point. Since C does all passing of
>> floats as doubles, and does all math in double
Jonathan Polley wrote:
>
...
>
> Aside from removing unreferenced variables, the bulk of the changes were
> in the area of the use of floating-point. Since C does all passing of
> floats as doubles, and does all math in double, could we have a mandate
> that all floating-point valued be double?
I have FlightGear building without warnings under MSVC, with the following
exceptions:
FDM/ExternalNet.cxx has two byte-order conversion on bool. What size is
bool? I know, I could instrument the code, but it is getting late.
FDM/UIUCModel/uiuc_menu.cpp: the check_float() function doesn't lo
At 4/14/02, you wrote:
>I will volunteer for making the MSVC patches for all the areas but
>panel.cxx and the FDMs. The file panel.cxx has NONE defined as a macro
>and the chance is too high for me to mess something up in the FDMs (and
>they are under active development). I will also not touc
Jonathan Polley writes:
> The file panel.cxx has NONE defined as a macro
Actually, the file explicitly *un*defines NONE as a macro so that it
won't interfere with properly-scoped enumerated values from
elsewhere. I don't know if that's still necessary -- it's worth a
quick test.
> 'class ss
I will volunteer for making the MSVC patches for all the areas but
panel.cxx and the FDMs. The file panel.cxx has NONE defined as a macro
and the chance is too high for me to mess something up in the FDMs (and
they are under active development). I will also not touch type mismatches
such as:
Jonathan Polley writes:
> My preference would be to have me keep the list fo MSVC build errors
> up-to-date and come up with a deadline when certain errors will be fixed
> (especially the ones in FDM\LaRCsim\ls_model.c).
Patches are best (for me; full files if you send to Curt). If you
sim
On Sunday, April 14, 2002, at 03:42 AM, Erik Hofman wrote:
> Jonathan Polley wrote:
>
>> I can easily submit patches for the more obvious errors (eliminating
>> unreferenced local variables, adding some type casts), but I don't feel
>
> Well, that can be problemeatic, since it might hide other
Jonathan Polley wrote:
> I can easily submit patches for the more obvious errors (eliminating
> unreferenced local variables, adding some type casts), but I don't feel
Well, that can be problemeatic, since it might hide other problems if
changed without knowing the code well enough ...
Erik
On Saturday, April 13, 2002, at 02:39 PM, David Megginson wrote:
> Jonathan Polley writes:
>
>> I know that there was some discussion on this topic just after the
>> 0.7.9 release, but I don't remember the outcome (or if there was
>> one). Will the next release be feature adding, or bug squashi
Jonathan Polley writes:
> I know that there was some discussion on this topic just after the
> 0.7.9 release, but I don't remember the outcome (or if there was
> one). Will the next release be feature adding, or bug squashing,
> release? The reason that I am asking is because of the warning
I know that there was some discussion on this topic just after the 0.7.9
release, but I don't remember the outcome (or if there was one). Will the
next release be feature adding, or bug squashing, release? The reason
that I am asking is because of the warnings that I see begin generated by
M
15 matches
Mail list logo
