-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LFE's having a hard time including lager.hrl #99
Comments
These will be neccessary until this bug is fixed: * lfe/lfe#99
Half of the problem has been solved.
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. |
Awesome, Robert -- thanks! |
Fixed with logjam, no? |
@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? |
Ah, right... I wonder how we might support parse transforms. I suppose we might have to transform the parse transforms first. 🙃 |
I just checked, and it's still a problem: > (include-file "include/lager.hrl")
1: Warning: unable to translate macro 'INT_LOG'
LEVEL2NUM |
😞 Thanks for checking. |
The logjam work-around uses older lager for logjam + older Erlang versions. For newer versions of Erlang that support the new Closing. |
Here's the error in the REPL:
Something similar happens when I try to include it in a file and then compile. In the code:
(include-file "deps/lager/include/lager.hrl")
And the compile output:
Here's a copy of the
hrl
file.The text was updated successfully, but these errors were encountered: