From: "Tom Browder" <tom.browder@gmail.com>
To: "Michael Kaes" <michael.kaes@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Template type usage from base classes
Date: Tue, 19 Aug 2008 23:54:00 -0000 [thread overview]
Message-ID: <8bc817ee0808191619yb78fbepb67e365664364b4e@mail.gmail.com> (raw)
In-Reply-To: <9c1eb01c0808190944n35fdee8fwb8543488abae948e@mail.gmail.com>
On Tue, Aug 19, 2008 at 11:44 AM, Michael Kaes <michael.kaes@gmail.com> wrote:
> Thanks everybody,
>
> works as it I expected it :-)
> Took me nearly a day. I should stick more to gcc than to VS8.
I've had similar experiences with a cross-platform project where my
coworker is doing the Windows part and I'm doing the Linux part.
I get gcc-4.3.1 warnings and errors that he doesn't get *until* he
uses the /Za argument to his MSVC++ 2005 compiler.
-Tom
prev parent reply other threads:[~2008-08-19 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 15:37 Michael Kaes
2008-08-19 16:17 ` Eljay Love-Jensen
2008-08-19 16:17 ` Gian Lorenzo Meocci
2008-08-19 16:57 ` Michael Kaes
2008-08-19 23:54 ` Tom Browder [this message]
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=8bc817ee0808191619yb78fbepb67e365664364b4e@mail.gmail.com \
--to=tom.browder@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=michael.kaes@gmail.com \
/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: link
Be 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).