All,
I suggest to drop support for VS versions 8.0 and 9.0 in the master
branch. VS 10, 12/13 and 14/15 will still be supported.
Dmitry
--
Mobile security can be enabling, not merely restricting. Employees who
bring t
16.05.2016 00:17, Dimitry Sibiryakov wrote:
>
> But for 4.0 official compiler is VS 2013 which support that.
But we maintain projects for older VS versions too, and the code must be
compilable with them.
Dmitry
--
Mob
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
> http://ariya.ofilabs.com/2015/01/c-class-and-preventing-objec
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
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
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 cann
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 securit
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 sup
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, Adriano dos Santos Fernande
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 C
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
Projec
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
12 matches
Mail list logo
