So the data should include a flag to tell what endian form it is, and the code should be written to support both ways? Image file formats specify and endianness in the specification, not the files. If it's in the files, then you'd need code to handle both ways...
On Sun, 2005-03-27 at 09:28 -0500, Norman Vine wrote: > Paul Kahler writes: > > > > Never block transfer a structure by providing a pointer and size, there > > is simply no way for that to work cross-platform. > > Please .... > > That this isn't true is amply demonstrated by all the > images that get passed around the net :-) > > All one needs to do is make sure that the endian > order of the data is well defined ! > > There are many ways to do this perhaps the easiest > is to just use a 'magic' cookie at the beginning of the > data structure *or* have a well defined structure that > insures a certain endian order is imposed on the > creator. > > Cheers > > Norman > > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > _______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
