LFE's having a hard time including lager.hrl about lfe HOT 8 CLOSED

Half of the problem has been solved.

• The #(unbound_func #(extend-module 1)) comes from a new form I have added which the shell didn't recognise and so tried to evaluate it as a function. extend-module allows you to add module information (exports, attributes, etc) not only in the top define-module but in different places as well and the compiler collects and combines them later.
• The Warning: unable to translate macro 'INT_LOG' I think is because the body of the macro consists of 2 expressions (perfectly legal) and at the moment I only handle macros whose body consists of 1 expression. I will fix it.

I have restructured the lfe repo a little and you can get the latest version with improved code generation in the develop branch. The lfe-dev branch will disappear soon and there will soon be an lfe-dialyzer branch which contains some dialyzer interface modules, and the normal develop.

from lfe.

Awesome, Robert -- thanks!

from lfe.

Fixed with logjam, no?

from lfe.

@yurrriq Well, logjam offers what is essentially a work-around...

It would be nice if LFE was capable of addressing the two bullet points @rvirding outlined above (and I think it does now).

Maybe the other half of the problem to which Robert referred is the Erlang parse transforms (used by lager) which LFE can't do anything about?

from lfe.

Ah, right... I wonder how we might support parse transforms. I suppose we might have to transform the parse transforms first. 🙃

from lfe.

I just checked, and it's still a problem:

> (include-file "include/lager.hrl")
1: Warning: unable to translate macro 'INT_LOG'
LEVEL2NUM

from lfe.

😞 Thanks for checking.

from lfe.

The logjam work-around uses older lager for logjam + older Erlang versions.

For newer versions of Erlang that support the new logger module, logjam just uses that.

Closing.

from lfe.