From -2476272685936043890 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,290ced9644daa112 X-Google-Attributes: gidf78e5,public From: Hubert HOLIN Subject: Re: Types with Bit-Sizes Date: 1998/03/17 Message-ID: <350D5D85.E19B7522@ArtQuest.fr>#1/1 X-Deja-AN: 334712815 Content-Transfer-Encoding: 7bit References: <35084BDC.4108978E@verisim.com> X-Original-Date: Mon, 16 Mar 1998 18:12:37 +0100 Content-Type: text/plain; charset=us-ascii Organization: ArtQuest X-Auth: PGPMoose V1.1 PGP comp.std.c++ iQBFAgUANQ2/V+EDnX0m9pzZAQEo/gGAm51jDkvbKilgYEi7pjWXX4DZoCo5AffB X8QMzzIyExewLi/iJkH2YFzaHAFHu1Kp =OgLK Mime-Version: 1.0 Reply-To: hh@ArtQuest.fr, holin@mathp7.jussieu.fr Newsgroups: comp.std.c++ Paul Hamilton wrote: [SNIP] > This get's mentioned quite often around C++, but the reality is that > passing structs between machines is a really bad idea. Passing data (such as graphic files) between machines is customary and necessary. Thankfully, M$ does not dominate to such an extant that only one platform needs to be considered. [SNIP] > Relying on bit/byte size, or even the fact that structures will actually > stay the same size, with members in the same positions between revs of > compilers/code bases is not realistic. Knowing the bit-size of your data is an appreciated help when you do integer-based computations (it insures bound checks, for instance). C++ does need this feature (and an officialization of 64 bits "long long"s...). Hubert Holin holin@mathp7.jussieu.fr --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html ]