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.
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.