Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command-line Interface doesn't exist. #1

Open
acertain opened this issue Nov 26, 2012 · 1 comment
Open

Command-line Interface doesn't exist. #1

acertain opened this issue Nov 26, 2012 · 1 comment
Assignees
Labels

Comments

@acertain
Copy link

The command-line interface documented in README doesn't exist.

@mrluc
Copy link
Owner

mrluc commented Nov 26, 2012

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.

@ghost ghost assigned mrluc Nov 26, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants