Filter out parse_transforms from compilation options

[djnym]

I apply a local parse_transform to almost all my code which adds a -vsn() to the code. When I attempt to use meck on one of these I get a compilation exception. After some investigation (involving adding [verbose, report_errors, report_warnings] to the compile options, something you may consider doing as a convenience).

I discovered it was because the parse transform was not in the code path. Attempts to add paths and things like that seemed annoying at best, and hard to make general. However, the parse_transforms have already been applied to the forms which meck is modifying, so compiling with them again doesn't make any sense. So I filter them out.

[eproxus]

I originally left out those compilation options because I don't like when libraries like this are verbose and print out things to the console. It tends to mess up test output etc. However, a good idea might be to add an {compile, Options} option to meck?

[djnym]

Alternatively in the error clause of compile_and_load_forms you could do something like

Error ->
  % compile again with verbose reporting
  compile:forms (AbsCode, [verbose, report_errors, report_warnings | Opts])

So if an error occurs you get more information. However, if you did add the option, then you could do something like add a parse transform to the meck compilation (just make sure you add in the options post filtering out of parse_transforms ;)), which might be useful to someone someday.

[eproxus]

Did discover that there's also the options return_errors and return_warnings (or the short return for both). Those could be printed if returned (at least the errors, compiler warnings are not uncommon, especially for code you don't control).

The parse transform of mocked modules is a great idea! That would justify the {compile, Options} flag in itself.