Notes

[fenollp]

Feel free to split this in multiple issues…

• [ ] Target Core Erlang instead of Erlang's AST
• [ ] Explain with words what Interfix is (not just examples)
• [x] Do not include generated lexer and parser .erl in src, but edit your Makefile
• [x] API functions are the one you export, all the others are internal functions. At least interfix.erl got it wrong.

[marianoguerra]

first of all, thanks for having interest in the project.

will reply on each item below.

Target Core Erlang instead of Erlang's AST

which are the pros to migrate to Core Erlang?

Here I list the reason I use Erlang's AST:

• Translates to all the intermediate representations below for free (including core erlang)
• Translation to idiomatic Erlang source code for free
• can use all Erlang tooling, for example:
  • parse transforms
  • erlang compiler's errors and warnings checker
  • xref and dialyzer
• I know it :p

Explain with words what Interfix is (not just examples)

opening a ticket #4

Do not include generated lexer and parser .erl in src, but edit your Makefile

will exclude lexer and parser's output #5

what do you mean by "but edit your Makefile"

API functions are the one you export, all the others are internal functions. At least interfix.erl got it wrong.

until recently this was an experiment so the only API was the escript to translate it, now that I realized there's no reason for it to be a full language with time I will expose an actual API and some rebar3 plugins. #6 and #7

[marianoguerra]

@fenollp no docs yet, but if you read this section https://github.com/marianoguerra/interfix#cli-reference and use it to play with the files on the examples folder you can get a sense of what's going on :)