This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Undefined ref to 'function<void ()()>::operator()() const' when called from free function defined in cc file.

From: "Peter Dimov" <pdimov at mmltd dot net>
To: "Chris Fairles" <chris dot fairles at gmail dot com>
Cc: "libstdc++" <libstdc++ at gcc dot gnu dot org>
Date: Fri, 29 Aug 2008 16:49:52 +0300
Subject: Re: Undefined ref to 'function<void ()()>::operator()() const' when called from free function defined in cc file.
References: <fac6bb500808290541nf3184adr7bdc6b06a1673d7a@mail.gmail.com> <002201c909d9$f972bfd0$6901a8c0@pdimov> <fac6bb500808290632o26fe6dafv50707fbda4a12a3e@mail.gmail.com>

Chris Fairles wrote:

Yeah. I'm not a huge fan of this global function<> w/ mutex method...

The main drawback I see is that function<>'s (copy) constructor or assignment operator are allowed to throw. You could std::move in __once_proxy though.

References:
- Undefined ref to 'function<void ()()>::operator()() const' when called from free function defined in cc file.
  - From: Chris Fairles
- Re: Undefined ref to 'function<void ()()>::operator()() const' when called from free function defined in cc file.
  - From: Peter Dimov
- Re: Undefined ref to 'function<void ()()>::operator()() const' when called from free function defined in cc file.
  - From: Chris Fairles

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]