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

Feature Request: Add a compilation blacklist of sorts #38

Open
XxX-Daniil-underscore-Zaikin-XxX opened this issue Sep 24, 2024 · 1 comment

Comments

@XxX-Daniil-underscore-Zaikin-XxX
Copy link
Contributor

XxX-Daniil-underscore-Zaikin-XxX commented Sep 24, 2024

Incremental compilation is super cool. Pyro is a cool tool that already makes this happen.

However, it does this by parsing the .ppj file and feeding Caprica curated old-school command-line options. Although Caprica can now work with .ppj files itself, this feature is redundant because bypassing that functionality is the most optimal way to use Capria.

If Caprica had a way of blacklisting already-compiled scripts, though, that'd change things. Pyro could pass Caprica the .ppj and the blacklist, and that'd be that.

Alternatively, Caprica could handle that on its own, though this would be redundant and a pain to implement.

@XxX-Daniil-underscore-Zaikin-XxX
Copy link
Contributor Author

One issue is Pyro's remote Import feature. There'd be no "good" way to slot that into Caprica anywhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant