I would like to see more use cases before adding a core compiler to the language. In particular, if you are writing your own language, it is most likely that sooner rather than later you will have your own compiler on top of core and then you won't use the core compiler at all.
*José Valim* www.plataformatec.com.br Skype: jv.ptec Founder and Director of R&D On Thu, Jul 14, 2016 at 11:28 PM, Chris Keele <d...@chriskeele.com> wrote: > Hey all! > > I've recently decided to sit down and try to make a toy language. > Intrigued by a 2014 Robert Virding talk, and having a working AST in yecc > and leex, I thought I'd play around with trying to compile it to Core > Erlang. > > In order to expedite learning about Core Erlang I decided to try to make a > mix compiler for it for quicker feedback cycles, so I took a look at the > Mix Erlang Compiler, and boy do I have no clue what's going on there. But I > went in and tweaked hardcoded references to 'erl' and passed a command line > flag in to the main compiler until I got something that worked. > > I've had far less luck mimicking the test suite for the the Erlang > Compiler task, but I can safely say my code works 100% of the time for the > 1 hello world program I've tried it on once. The changes relevant to making > the Erlang Compiler handle Core Erlang instead can be found here > <https://github.com/christhekeele/mix_core_compiler/compare/613f3d9103d57281df10a65de096ce2e052d5ca0...543c56641f431a8025cb79624bb6a2918e31a62b>, > and as you can see they're pretty minimal. > > I'm wondering if > > - We'd actually want this in core, and if so > - If the Erlang Compiler could be parameterized to handle this case as > well, or > - If a new compiler might make more sense > > If consensus is this rightly belongs nowhere near core, I'd always > appreciate some pointers on how I can improve what I have, or just any > illumination into the compiler manifest code lifecycle, since I'll probably > be using my code for a fair bit of experimentation over the next several > weeks. > > -- > You received this message because you are subscribed to the Google Groups > "elixir-lang-core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elixir-lang-core+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elixir-lang-core/bea2c78a-31d5-4cac-b271-6142b668a115%40googlegroups.com > <https://groups.google.com/d/msgid/elixir-lang-core/bea2c78a-31d5-4cac-b271-6142b668a115%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4LTotKcPFwqnHRO2675Ra2BMR%3D4xYDnRdeWNk%3DB2VoVpw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
