Re: [boost] workaround for bind/gcc warnings

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-01-17 08:40:52

No, of course not. In a real fix you would always define arg_1...arg_N, and
only conditionally define _1..._N.
Of course it means that portable library code which wants to use bind has to
avoid _1..._N.

----- Original Message -----
From: "Peter Dimov" <pdimov_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Thursday, January 17, 2002 8:32 AM
Subject: Re: [boost] workaround for bind/gcc warnings

> From: "David Abrahams" <david.abrahams_at_[hidden]>
> > From: "Peter Dimov" <pdimov_at_[hidden]>
> >
> > > > // All compilers; I need portable code
> > > > file:// # if ((__GNUC__ == 3) && (__GNUC_MINOR__ == 0))
> > > > #  define _1 arg_1
> > >
> > > I'd _hate_ to do that. Isn't there a way out? g++ folks acknowledged
the
> > > warning to be a bug, didn't they?
> >
> > Yes, but our friends failed to address it for 3.0.3 :-(
>
> Do you need a solution for this release? I want to give it more thought.
> #define _1 arg_1 isn't going to attract many followers. ;-)
>
> --
> Peter Dimov
> Multi Media Ltd.
>
>
> Info: http://www.boost.org  Send unsubscribe requests to:
<mailto:boost-unsubscribe_at_[hidden]>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>