[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1409071356290.30149@monopod.intra.ispras.ru>
Date: Sun, 7 Sep 2014 14:05:19 +0400 (MSK)
From: Alexander Monakov <amonakov@...ras.ru>
To: musl@...ts.openwall.com
Subject: Re: [PATCH 1/9] interface additions for the C thread
implementation
On Sun, 7 Sep 2014, Jens Gustedt wrote:
> > > For the C++ API/ABI, these also are different types, now, with type names
> > > (that are used for name mangling, e.g) as listed above.
> > >
> > > Somebody better versed in C++ could perhaps contribute code that
> > > overloads the comparison and assignment operators such that a compilation
> > > that tries to compare or copy these types fails.
> >
> > I'm not sure what you meant by this last paragraph.
>
> AFAIR in C++ there are ways to inhibit usage of copy assignment by
> declaring some "operator=" function that is never defined. But my C++
> has really become rusty.
There's no need to do that since those are unrelated structs, and therefore no
operator== and operator= are available in the first place. You also can't do
that in C (but in C++ you get an error rather than a warning when trying
to assign pointers).
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
