Pete wrote:
Yeah, sorry, I was mucking about and did a few test runs with some
int->long changes. That's one of them. However, I can't believed I
missed the template int in there. Dumb, but maybe that will help.
As for the int,long,string, whatever. There should be a somewhat
portable way to do this. When I did this for a 32 to 64 bit port at
work, we just changed them all to long's because we knew the Intel and
GCC compilers both treated longs == pointers. I find it odd that the
Win compiler will treat long == int because that provides no standard
C/C++ 64 integer. If that's the case, then do they have a new type to
store a 64 bit integer, or do they use some other magic?
Anyway, the lesson is to never assume a pointer size cause it will
bite you eventually. Thanks.
Mathias Fröhlich wrote:
Hi,
strange:
my recent checkout contains a FGAIBase::_getID() function returning
an int not a long. Have you modified that?
And with that, the constructor
SGRawValueMethods<FGAIBase,int>(*this, &FGAIBase::_getID)
should exist.
If you want to make _getID return a long, you have to change that to:
SGRawValueMethods<FGAIBase,long>(*this, &FGAIBase::_getID)
That did it. Thanks for pointing that out. Up and running now.
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
