On 02/26/2016 05:16 PM, Dimitry Sibiryakov wrote:
> 26.02.2016 14:51, Alex Peshkoff wrote:
>> Better keep Array 'public AutoStorage'.
> But in this case every derived class will have to declare constructor
> with call to
> getDefaultMemoryPool() inside which is more than necessary.
>
Yes, it
26.02.2016 14:51, Alex Peshkoff wrote:
> Better keep Array 'public AutoStorage'.
But in this case every derived class will have to declare constructor with
call to
getDefaultMemoryPool() inside which is more than necessary.
--
WBR, SD.
---
On 02/26/2016 04:43 PM, Dimitry Sibiryakov wrote:
> 26.02.2016 14:21, Dimitry Sibiryakov wrote:
>> This word is not in GlobalStorage declaration, but in "class Array
>> : protected Storage".
> What is better: change declaration of Array or re-declare the operators
> in every
> derived class?
>
26.02.2016 14:21, Dimitry Sibiryakov wrote:
> This word is not in GlobalStorage declaration, but in "class Array
> : protected Storage".
What is better: change declaration of Array or re-declare the operators in
every
derived class?
--
WBR, SD.
--
26.02.2016 14:11, Alex Peshkoff wrote:
> Where is word protected?
Oops, you are right. This word is not in GlobalStorage declaration, but in
"class Array
: protected Storage".
--
WBR, SD.
--
Site24x7 APM Insight
On 02/25/2016 07:03 PM, Dimitry Sibiryakov wrote:
> Hello, All.
>
> Comment on subj says that
>
>> // Global storage makes it possible to use new and delete for classes,
>> // based on it, to behave traditionally, i.e. get memory from permanent
>> pool.
> But at the same time
Hello, All.
Comment on subj says that
> // Global storage makes it possible to use new and delete for classes,
> // based on it, to behave traditionally, i.e. get memory from permanent
> pool.
But at the same time new and delete are declared protected that makes them
impos
