[erlang-questions] dialyzer for lisps (Re: If you are homesick for object.selector)
Mon Jan 28 02:42:37 CET 2013
Making read it read source files from other front-ends which generate core erlang would not be too difficult. The main problem is that it is hard-coded that dialyzer assumes that source files end with .erl.
I thought a bit about generating Erlang instead of Code for LFE but came to the conclusion that the resulting Erlang would not be very transparent anyway.
----- Original Message -----
> From: "Anthony Ramine" <>
> To: "Raoul Duke" <>
> Cc: "erlang-questions Questions" <>
> Sent: Sunday, 27 January, 2013 11:01:01 PM
> Subject: Re: [erlang-questions] dialyzer for lisps (Re: If you are homesick for object.selector)
> Patching Dialyzer to make it work on Core Erlang should be pretty
> straightforward as it does its analysis on Core Erlang code anyway;
> it's just that it doesn't currently know how to obtain it from the
> BEAM file without first getting the Erlang AST chunk and compiling
> it to Core Erlang AST.
> Anthony Ramine
> Le 27 janv. 2013 à 22:17, Raoul Duke a écrit :
> >> This makes it impossible to use both Erlang's built in debugger
> >> and
> >> Dialyzer on things compiled to Core Erlang. It could be argued
> >> that
> >> this isn't a major problem. In Joxa, at least, the lack of those
> >> features have been somewhat painful for new folks.
> > i would argue it is clearly a giant problem. i don't mean that i'm
> > mad
> > at joxa, i'm just saying *any* language that doesn't have a
> > debugger
> > is not a real language. but furthermore, anything in the erlang
> > ecosystem that can't work with dialyzer is to my mind a bit of a
> > non-starter. ¥2.
> > _______________________________________________
> > erlang-questions mailing list
> > http://erlang.org/mailman/listinfo/erlang-questions
> erlang-questions mailing list
More information about the erlang-questions