2005/10/16, Erik Hofman [EMAIL PROTECTED]:
Thanks for the patch Ladislav, I've committed a slightly modified
version to CVS now.
Erik
Not at all.
Just I am not sure about computing of geoc in src/Scenery/hitlist.cxx .
Regards Ladislav.
___
Ladislav Michnovič wrote:
Hello.
Using new gcc 4.0 I have some serios warnings about uninitialized
variables, that are used. I created a patch, but I have no idea if it
is possible to do it my way. Can you check this out please? It would
be great if it will be fixed in next release. The CVS
Hello.
Using new gcc 4.0 I have some serios warnings about uninitialized
variables, that are used. I created a patch, but I have no idea if it
is possible to do it my way. Can you check this out please? It would
be great if it will be fixed in next release. The CVS doesn't differ
in this case
Fred,
You are correct. However, neither are they classes written by the user. And we
routinely get headaches from automatic int, float, pointer variables we forgets
to initialize. On the other hand, we do expect the opposite of class objects. In
fact, the whole point of a c'tor is that default
Flightgear bombs when JSB outputs data in CSV format with MSVC 6 (latest
change to c172.xml r1.38).
It appears that the coefficient kCLge 'Change_in_lift_due_to_ground_effect'
has a value derived from FGPosition::hoverbmac which is unitialized.
The segmentation violation is in
Flightgear bombs when JSB outputs data in CSV format with MSVC 6 (latest
change to c172.xml r1.38).
It appears that the coefficient kCLge 'Change_in_lift_due_to_ground_effect'
has a value derived from FGPosition::hoverbmac which is unitialized.
Fixed. Will be committed later this evening.
Flightgear bombs when JSB outputs data in CSV format with MSVC 6 (latest
change to c172.xml r1.38).
It appears that the coefficient kCLge
'Change_in_lift_due_to_ground_effect'
has a value derived from FGPosition::hoverbmac which is unitialized.
Fixed. Will be committed later this
Christian Mayer wrote:
Frederic Bouvier wrote:
but I think that every member variables should have a default value set in
class constructor
Definitely!! I had many troubles with MSVC and uninialized variables so
far.
C'tors that don't initialize class members? Ought to have a good
C'tors that don't initialize class members? Ought to have a good
reason for that
in the class documentation. Otherwise one is writing time bombs
in the code.
I believe most class members are properly initialized. There are some that
may not appear to be, though - that is, the vector and
