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

[Brujo Benavides]

Strangely enough, this actually generates a different warning:

-module(weird).
-define(PLEASE_DONT).
-ifdef(PLEASE_DONT).
-compile({parse_transform,undefined_parse_transform}).
-endif.

1> c(weird).
src/weird.erl:2: badly formed 'define'

> On Jan 30, 2017, at 12:27, Brujo Benavides <fernando.benavides@REDACTED> wrote:
> 
> Well… this on the other hand, compiles:
> 
> -module(weird).
> -define(PLEASE_DONT, true).
> -ifndef(PLEASE_DONT).
> -compile({parse_transform,undefined_parse_transform}).
> -endif.
> 
>> On Jan 30, 2017, at 12:24, <john.hughes@REDACTED <mailto:john.hughes@REDACTED>> <john.hughes@REDACTED <mailto:john.hughes@REDACTED>> wrote:
>> 
>> 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!
>>  
>> John
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED <mailto:erlang-questions@REDACTED>
>> http://erlang.org/mailman/listinfo/erlang-questions
> 

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