[erlang-questions] Disabling a parse transform on a per-file basis?

[Roger Lipscombe]

It would indeed be an undefined function, rather than a compile error.
Good point, thanks.

It would, however, have died with an obvious error in development,
rather than deadlocking in production and paging me while I was
enjoying a pleasant glass or two of wine :-)

Oh well.

Thanks,
Roger.

On 17 August 2015 at 09:05, Luis Rascão <luis.rascao@REDACTED> wrote:
> Hi Roger,
> From what i can see, there is no way to disable a parse transform on a
> per-file
> basis. Even if there was you would get no compile errors, just undefined
> functions
> at runtime.
>
> On Mon, Aug 3, 2015 at 1:58 PM, Roger Lipscombe <roger@REDACTED>
> wrote:
>>
>> It turns out that you can deadlock lager (2.0.3) if you attempt to use
>> lager:log (or lager:debug, etc.) from inside a lager backend.
>>
>> I have the lager parse transform enabled in rebar.config for every
>> module in the application.
>>
>> Is there a way to *remove* it for specific modules? Then, if anyone
>> attempts to use it in one of our lager backends, they'll get a compile
>> error, rather than a deadlock in production.
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>
>
>
>
> --
> PGP fingerprint: F708 E141 AE8D 2D38 E1BC  DF3D 1719 3EA0 647D 7260