Re: [Firebird-devel] Non-copyable objects

2016-05-15 Thread Dmitry Yemanov
15.05.2016 00:59, Adriano dos Santos Fernandes wrote: > > Instead of write private copy constructor and operator=, what about > start using a mixing at least for new code? > > It makes easier and much more clear. > > Example taken from >

Re: [Firebird-devel] Non-copyable objects

2016-05-15 Thread Adriano dos Santos Fernandes
Em 15/05/2016 18:27, Dimitry Sibiryakov escreveu: > 15.05.2016 23:21, Adriano dos Santos Fernandes wrote: >> Current compilers supports std library and we cannot use it, so because > it supports doesn't matter. > >"We don't use library X, so we cannot use language Y" you said. It is a > very

Re: [Firebird-devel] Non-copyable objects

2016-05-15 Thread Dimitry Sibiryakov
15.05.2016 23:21, Adriano dos Santos Fernandes wrote: > Current compilers supports std library and we cannot use it, so because it supports doesn't matter. "We don't use library X, so we cannot use language Y" you said. It is a very strange logic or I misunderstood you completely. Deleted

Re: [Firebird-devel] Non-copyable objects

2016-05-15 Thread Adriano dos Santos Fernandes
Em 15/05/2016 18:17, Dimitry Sibiryakov escreveu: > 15.05.2016 23:14, Adriano dos Santos Fernandes wrote: >> First, we do not use C++ version with this support. > >For 3.0 - yes. But for 4.0 official compiler is VS 2013 which support that. > Current compilers supports std library and we

Re: [Firebird-devel] Non-copyable objects

2016-05-15 Thread Dimitry Sibiryakov
15.05.2016 23:14, Adriano dos Santos Fernandes wrote: > First, we do not use C++ version with this support. For 3.0 - yes. But for 4.0 official compiler is VS 2013 which support that. -- WBR, SD. -- Mobile

Re: [Firebird-devel] Non-copyable objects

2016-05-15 Thread Adriano dos Santos Fernandes
Em 15/05/2016 08:15, Egor Pugin escreveu: > My vote is for explicit '= delete' solution too. Without any base > classes like NonCopyable. > Maybe sometimes you want allow copy init (clone members) and deny copy > assignment (deny following clones). > First, we do not use C++ version with this

Re: [Firebird-devel] Non-copyable objects

2016-05-15 Thread Egor Pugin
My vote is for explicit '= delete' solution too. Without any base classes like NonCopyable. Maybe sometimes you want allow copy init (clone members) and deny copy assignment (deny following clones). On 15 May 2016 at 13:17, Dimitry Sibiryakov wrote: > 14.05.2016 23:59,

Re: [Firebird-devel] Non-copyable objects

2016-05-15 Thread Dimitry Sibiryakov
14.05.2016 23:59, Adriano dos Santos Fernandes wrote: > Instead of write private copy constructor and operator=, what about > start using a mixing at least for new code? > > It makes easier and much more clear. Even easier and clearer explicitly deleted constructor and operator: Car(const

[Firebird-devel] [FB-Tracker] Created: (CORE-5239) Add virtual table SEC$ROLES to return all roles currently active for the connected user

2016-05-15 Thread Dmitry Yemanov (JIRA)
Add virtual table SEC$ROLES to return all roles currently active for the connected user --- Key: CORE-5239 URL: http://tracker.firebirdsql.org/browse/CORE-5239

[Firebird-devel] [FB-Tracker] Created: (CORE-5238) Replace xinetd support with the native listener

2016-05-15 Thread Dmitry Yemanov (JIRA)
Replace xinetd support with the native listener --- Key: CORE-5238 URL: http://tracker.firebirdsql.org/browse/CORE-5238 Project: Firebird Core Issue Type: Task Environment: POSIX Classic