Martin Spott writes: > "Curtis L. Olson" <[EMAIL PROTECTED]> wrote: > > Martin Spott writes: > >> Maybe sometime someone finds the time to 'normalize' this interface to make > >> it platform independent ;-) > > > Could you be more specific? The routines already support network byte > > order, however there are cases (i.e. interfacing to an external perl > > script using pack/unpack, where network byte order is not desirable) > > so I'd like to keep this optional. > > O.k., I understand. But what am I going to do when the 'client' runs on a > different platform with different byte order where an int probably has a > different size (say a PPC750) ? You know that I can't decide to stick to one > plaform ;-) > It's just a thought with platform interoperability in mind. But if I really > start flight trainig this idea probably becomes obsolete because I won't > have the time and money to proceed with my project ....
I just don't have the time right now to do 10x the work, just to support a situation that *might* possibly occur in the future. Most people that are going to link up machines for some "serious" purpose, are likely to buy similar machines. Also, doesn't the C/C++ standard define an int and float to be 4 bytes? I think we cover most reasonable/expected cases right now, and if we do run into something different in the future, then I think it would make sense to spend the effort at that time. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities curt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
