[erlang-questions] Logging methods in Erlang (FUNCTION macro)

Steve Vinoski vinoski@REDACTED
Sat Sep 6 01:19:03 CEST 2014

On Fri, Sep 5, 2014 at 6:41 PM, Loïc Hoguin <essen@REDACTED> wrote:

> On 09/05/2014 11:25 PM, Michael Truog wrote:
>>  2) Use a parse transform to rewrite all the source code that wants to do
>> logging so that it can determine whether it needs to log by checking
>> global state, probably in ets.  This approach is taken in lager with the
>> parse transform at
>> https://github.com/basho/lager/blob/master/src/lager_transform.erl .
> I do not like this one, especially since lager will simply fail if modules
> were not compiled with the parse_transform (the functions aren't defined).
> So you have to compile everything with it, can't call from the shell (at
> least not the same way), yada yada. Very impractical. Efficiency is always
> good to have but that one is quite costy.

Instead of complaining in text, how about contributing in code? If there's
something you don't like about lager, Andrew is easy to find in IRC or on
email -- discuss your concerns with him, propose a solution, and submit a
PR. Andrew is quite reasonable and pragmatic.

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

More information about the erlang-questions mailing list