[erlang-questions] For your amusement--why doesn't this compile?

Alex S. <>
Mon Jan 30 16:50:48 CET 2017


It’s considered an unknown module attribute, and those aren’t errors.
> 30 янв. 2017 г., в 18:38,  написал(а):
> 
> So why isn’t that reported as an error?
>  
> John
>  
> From: Alex S. <mailto:>
> Sent: Monday, January 30, 2017 4:31 PM
> To:  <mailto:>
> Cc:  <mailto:>
> Subject: Re: [erlang-questions] For your amusement--why doesn't this compile?
>  
>  
>> 30 янв. 2017 г., в 18:24, < <mailto:>> < <mailto:>> написал(а):
>>  
>> Here’s a behaviour that’s had me tearing my hair today. Consider this module:
>>  
>> -module('Aaargh!!').
>> -define(PLEASE_DONT).
>> -ifndef(PLEASE_DONT).
>> -compile({parse_transform,undefined_parse_transform}).
>> -endif.
>>  
>> It fails to compile, with one simple error message:
>>  
>> 20> c('Aaargh!!').
>> Aaargh!!.erl: undefined parse transform 'undefined_parse_transform'
>> error
>>  
>> If you can see why, you’re more an Erlang wizard than I am!
>>  
> Easy enough, there’s no one-argument define().
>  
> Define it to true if you don’t care about the value.
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20170130/b92abf66/attachment.html>


More information about the erlang-questions mailing list