On 20/04/15 09:42, Stefan Schmidt wrote:
> Hello.
>
> On 17/04/15 18:07, Tom Hacohen wrote:
>> Hey,
>>
>> As you guys may have noticed, a few people have started using the
>> compiler #warning directive as their public TODO. I guess it makes
>> sense, because it's distributed and safer than a piece
Hello.
On 17/04/15 18:07, Tom Hacohen wrote:
> Hey,
>
> As you guys may have noticed, a few people have started using the
> compiler #warning directive as their public TODO. I guess it makes
> sense, because it's distributed and safer than a piece of paper. However
> it's really bad, and is pol
On Fri, 17 Apr 2015 17:07:55 +0100 Tom Hacohen said:
> Hey,
>
> As you guys may have noticed, a few people have started using the
> compiler #warning directive as their public TODO. I guess it makes
> sense, because it's distributed and safer than a piece of paper. However
> it's really bad,
Hey,
As you guys may have noticed, a few people have started using the
compiler #warning directive as their public TODO. I guess it makes
sense, because it's distributed and safer than a piece of paper. However
it's really bad, and is polluting our compiler output.
Just to give one example (ou
