On Monday, April 16, 2012 22:58:44 Andrei Alexandrescu wrote:
> On 4/16/12 9:20 PM, Jonathan M Davis wrote:
> > On Monday, April 16, 2012 19:57:04 Caligo wrote:
> >> So, since they haven't said anything, does this mean that neither
> >> Walter nor Andrei have the answer to this question? or is this
On 4/16/12 9:20 PM, Jonathan M Davis wrote:
On Monday, April 16, 2012 19:57:04 Caligo wrote:
So, since they haven't said anything, does this mean that neither
Walter nor Andrei have the answer to this question? or is this
something a lot more complicated ?
My guess is that they haven't read th
On Mon, Apr 16, 2012 at 9:20 PM, Jonathan M Davis wrote:
> On Monday, April 16, 2012 19:57:04 Caligo wrote:
>> So, since they haven't said anything, does this mean that neither
>> Walter nor Andrei have the answer to this question? or is this
>> something a lot more complicated ?
>
> My guess is t
On Monday, April 16, 2012 19:57:04 Caligo wrote:
> So, since they haven't said anything, does this mean that neither
> Walter nor Andrei have the answer to this question? or is this
> something a lot more complicated ?
My guess is that they haven't read the thread, but I don't know.
- Jonathan M
So, since they haven't said anything, does this mean that neither
Walter nor Andrei have the answer to this question? or is this
something a lot more complicated ?
Jonathan M Davis wrote:
> On Sunday, April 15, 2012 18:44:27 Jens Mueller wrote:
> > Jonathan M Davis wrote:
> > > I'd like to know which modifiers are considered to be storage classes. The
> > > term seems to be used on a lot more than actually qualifies (including
> > > using the term for the typ
On Sunday, April 15, 2012 18:44:27 Jens Mueller wrote:
> Jonathan M Davis wrote:
> > I'd like to know which modifiers are considered to be storage classes. The
> > term seems to be used on a lot more than actually qualifies (including
> > using the term for the type qualfiers: const, immutable, and
Jonathan M Davis wrote:
> I'd like to know which modifiers are considered to be storage classes. The
> term
> seems to be used on a lot more than actually qualifies (including using the
> term for the type qualfiers: const, immutable, and shared), and even the
> documentation uses it on stuff t
On Saturday, 14 April 2012 at 17:50:39 UTC, Jonathan M Davis
wrote:
On Sunday, April 15, 2012 01:49:09 Daniel Murphy wrote:
There's always the list in 'declaration.h'.
That's clearly not the list, since it includes const,
immutable, and shared,
which are type qualifiers rather than storage cl
On Saturday, 14 April 2012 at 17:50:39 UTC, Jonathan M Davis
wrote:
That's clearly not the list, since it includes const,
immutable, and shared,
which are type qualifiers rather than storage classes. It also
has stuff like
init in it, which isn't even vaguely a storage class. All of
the storage
On Sunday, April 15, 2012 01:49:09 Daniel Murphy wrote:
> "Jonathan M Davis" wrote in message
> news:mailman.1707.1334377994.4860.digitalmar...@puremagic.com...
>
> > I'd like to know which modifiers are considered to be storage classes. The
> > term
> > seems to be used on a lot more than actual
"Jonathan M Davis" wrote in message
news:mailman.1707.1334377994.4860.digitalmar...@puremagic.com...
> I'd like to know which modifiers are considered to be storage classes. The
> term
> seems to be used on a lot more than actually qualifies (including using
> the
> term for the type qualfiers:
I'd like to know which modifiers are considered to be storage classes. The term
seems to be used on a lot more than actually qualifies (including using the
term for the type qualfiers: const, immutable, and shared), and even the
documentation uses it on stuff that I wouldn't have thought would b
13 matches
Mail list logo
