From: Julian Smart <julians@redhat.com>
To: Richard Chan <cshihpin@dso.org.sg>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] g++-v3 and suspect C++ code in configtool
Date: Thu, 12 Jul 2001 03:33:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20010712113257.01a2ed00@pop> (raw)
In-Reply-To: <20010712104710.A5167@cshihpin.dso.org.sg>
At 10:47 AM 7/12/01 -0800, Richard Chan wrote:
>(I know 2.95.2 is the recommended version :-) but
>let's live on the edge here...after all
>if the C++ code is suspect but was passed by 2.95.2 shouldn't
>it be cleaned up?)
It certainly should, thank you very much for pointing out these problems!
>[Problem 1]
>friend X or friend class X declarations
>
>v3 is now fussy about "class" key-name - is this the behaviour expected
>by the standard?
Right, thanks. I'll add 'class' in the appropriate places.
>[Problem 2]
>operator overloading of + in w+e where w is a wxString and e is an
>ecFileName
>completely blows g++.
OK -- I will wrap variables in wxString temporaries where the wxString +
operator is the correct one to use.
Best regards,
Julian
--
Red Hat UK Ltd, Unit 200 Rustat House, 62 Clifton Road, Cambridge, UK. CB1
7EG Tel: +44 (1223) 271063
prev parent reply other threads:[~2001-07-12 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 19:41 Richard Chan
2001-07-12 3:33 ` Julian Smart [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=4.2.0.58.20010712113257.01a2ed00@pop \
--to=julians@redhat.com \
--cc=cshihpin@dso.org.sg \
--cc=ecos-discuss@sources.redhat.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).