public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Igor A. Goussarov" <igusarov@akella.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10332: Template classes are not instantiated correctly in presense of #pragma pack() Date: Tue, 15 Apr 2003 13:46:00 -0000 [thread overview] Message-ID: <20030415134600.17876.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10332; it has been noted by GNATS. From: "Igor A. Goussarov" <igusarov@akella.com> To: rittle@labs.mot.com Cc: velco@fadata.bg, ljrittle@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/10332: Template classes are not instantiated correctly in presense of #pragma pack() Date: Tue, 15 Apr 2003 17:39:08 +0400 Loren James Rittle wrote: > The proper fix is to either (a) document what is happening, > only available if no external spec says we are doing something wrong, > or (b) retain the global flag but capture it's value and bind it for > use when the C++ template is actually instantiated. The whole realm of #pragma is out of scope of the C++ standard. And I don't know which other documents could be considered relyable external specs... I can suggest examining the behaviour of other compilers (to keep the behaviour consistent) or taking this question of the correct behaviour to the trusted expert or community. Best Regards, Igor
next reply other threads:[~2003-04-15 13:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-15 13:46 Igor A. Goussarov [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-14 23:46 Loren James Rittle 2003-04-14 10:06 Igor A. Goussarov 2003-04-14 9:06 Momchil Velikov 2003-04-14 8:56 Igor A. Goussarov 2003-04-11 13:56 Momchil Velikov 2003-04-11 11:46 Igor A. Goussarov 2003-04-11 1:16 ljrittle 2003-04-07 10:46 igusarov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030415134600.17876.qmail@sources.redhat.com \ --to=igusarov@akella.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).