You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You're right - I'll update the README to be more specific for now, and see about patching this back in
In the short-term, an equivalent approach would be using the actual "macros.coffee" file itself -- ie, calling coffee ./node_modules/lib/macros.coffee filename. However, I think that it's actually broken; I haven't used command-line compiling myself much.
For context: I'm uneasy about compilation, I've been using this via require(), because I'm not happy with some of the questions that compilation raises -- ie, do we do an uglifyjs-style "load all files into a single, giant AST"? That way, macroexpansions would happen correctly across all files ... but making it happen safely, in a way that lets us split that AST apart into individual files at the end of the process -- or, producing only a single large file as output -- seems a bit ugly and complex.
The way it's set up now for CLI compiling, or the way that CoffeeScript does it, has the weakness that users have to carefully control the order of compilation, or some files that use macros may get compiled without their calls being expanded.
The command-line interface documented in README doesn't exist.
The text was updated successfully, but these errors were encountered: