Re: native code syntax extensions

[Raphael Proust <raphlalou@xxxxxxxxx>]

We could change lib/Makefile with:

-OFLAGS ?= -classic-display
+OFLAGS ?= -classic-display -tag warn_error_A -tag warn_A

This turns any warning into a compilation error and also turns all
warnings on. In my experience, the second tag makes it painful when
dealing with weird pattern matchings on complicated variants (because
you can't use the _ pattern anymore).

What do?

On 9/18/11, Dave Scott <Dave.Scott@xxxxxxxxxxxxx> wrote:
> Thanks for highlighting the warning btw, it sure does sound like a bug :)
> I'll investigate once I'm happy that the xenstore stuff works ok.
>
> --
> Dave Scott
>
> On Sep 17, 2011, at 12:31 PM, "Anil Madhavapeddy" <anil@xxxxxxxxxx> wrote:
>
>> On 17 Sep 2011, at 20:29, Raphael Proust wrote:
>>
>>> On 9/17/11, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
>>>> Great! What are the warnings?
>>>
>>> Mainly gcc on C files (left hand side of semi-colon has no effect,
>>> etc.). On ml files, only two (and not related to camlp4) :
>>>
>>> File "net/node/channel.ml", line 119, characters 8-11:
>>> Warning 26: unused variable fin.
>>
>> Ah yes, these were all present before. The C ones are due to libev, which
>> I'm going to replace with a select loop when I get back as its epoll(2)
>> backend seems completely broken on Linux.
>>
>>>
>>> File "fs/fat.ml", line 1051, characters 8-771:
>>> Warning 10: this expression should have type unit.
>>
>> This one's potentially more serious; are those directory updates meant to
>> be blocked on before proceeding in the thread, Dave?
>>
>> Anil
>>
>>
>>
>>
>


-- 
_______
Raphael