From:	DavMac AT iname DOT com (Davin McCall)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: -fpack-struct
Date:	Mon, 31 May 1999 05:33:09 GMT
Organization:	Monash Uni
Lines:	22
Distribution:	world
Message-ID:	<37521e6d.9390727@newsserver.cc.monash.edu.au>
References:	<l03130300b375f8976547@[145.98.116.66]> <l03130303b377583e9541@[145.98.116.90]>
NNTP-Posting-Host:	damcc5.halls.monash.edu.au
X-Trace:	towncrier.cc.monash.edu.au 928128757 21979 130.194.198.138 (31 May 1999 05:32:37 GMT)
X-Complaints-To:	abuse AT monash DOT edu DOT au
NNTP-Posting-Date:	31 May 1999 05:32:37 GMT
X-Newsreader:	Forte Free Agent 1.1/32.230
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

On Sun, 30 May 1999 23:16:04 +0200, Dlanor Blytkerchan <dlanor AT dds DOT nl>
wrote:

>I'm sorry: I don't mean to be picky or rude, but this doesn't help me much.
>Naturally I checked the FAQ first, which didn't help me much, as it
>recommends using an alternative sequence of members or the
>__attribute__((packed)) thingy, which amounts to the same thing as using
>the -fpack-struct compiler option. 

No it doesn't. __attribute__((packed)) affects only the specified
structures.

You mentioned that you were worried about using -fpack-structs because
it would cause problems with library functions that are passed/return
structures - but using __attribute__((packed)) on your own structures
would not affect the standard library structures (such as FILE) so the
library calls would work fine.

Davin.
__________________________________________________________
       *** davmac - sharkin'!! davmac AT iname DOT com ***
my programming page: http://yoyo.cc.monash.edu.au/~davmac/

- Raw text -