Simen kjaeraas wrote:
> On Sun, 27 Dec 2009 02:23:47 +0100, Ali Çehreli
wrote:
>
>> Simen kjaeraas wrote:
>> > On Sun, 27 Dec 2009 01:42:07 +0100, Ali Çehreli
>> wrote:
>> >
>> >> I've tested the following with dmd 2.037.
>> >>
>> >> The compiler generated opAssign is disabled by the defi
On Sun, 27 Dec 2009 02:23:47 +0100, Ali Çehreli wrote:
Simen kjaeraas wrote:
> On Sun, 27 Dec 2009 01:42:07 +0100, Ali Çehreli
wrote:
>
>> I've tested the following with dmd 2.037.
>>
>> The compiler generated opAssign is disabled by the definition of
>> opAssign(int). The compiler re
Simen kjaeraas wrote:
> On Sun, 27 Dec 2009 01:42:07 +0100, Ali Çehreli
wrote:
>
>> I've tested the following with dmd 2.037.
>>
>> The compiler generated opAssign is disabled by the definition of
>> opAssign(int). The compiler rejects the following assignment
>> operation. (The error message i
On Sun, 27 Dec 2009 01:42:07 +0100, Ali Çehreli wrote:
I've tested the following with dmd 2.037.
The compiler generated opAssign is disabled by the definition of
opAssign(int). The compiler rejects the following assignment operation.
(The error message is in the comment below.)
Is this b
I've tested the following with dmd 2.037.
The compiler generated opAssign is disabled by the definition of
opAssign(int). The compiler rejects the following assignment operation.
(The error message is in the comment below.)
Is this by design?
When I also define post-blit, the compiler genera
