Jon Berndt writes:
>
>> > Adding an ugly cast fixes the problem:
>> >
>> >   PropertyManager->Tie("forces/fbx-aero-lbs", this,1,
>> >     (double (FGAerodynamics::*)(int) const)
>&FGAerodynamics::GetForces);
>>
>> I'll roll that change into my copy until it gets made
>permanently.  While
>
>
>We'll do a little investigating, first. I want to understand why MSVC is
>having problems, first, when no other compiler appears to be complaining.
We
>want to remain as cross-platform/cross-compiler compatible as possible, but
>as a matter of policy, I am extremely hesitant to make crutches in our code
>to fix a crippled compiler - if, indeed, it turns out to be a problem with
>MSVC. Do you have any explanatory backup for why MSVC isn't working with
>this?

Jon, I don't think there is a 'conforming' compiler yet, and MSVC6 is
several years
old and I wonder how well the then current gnu stdlib++ would have handled
that
construct :-))

That said I will agree that MSVC6 even with all the service packs
is a 'little' behind most of the others in being able to handle some of
the more 'arcane' bits of C++.

There is STLPort however that should work just with just about any compiler
even MSVC :-)

http://www.stlport.org

Cheers

Norman


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

Reply via email to