Kevin Ballard schrieb:
> We could even add a
> --recompile-check flag that invokes GHC exactly as we're doing now, but
> unlike --force-recompile it won't actually recompile the custom yi if it
> doesn't have to.
Just to put in my two cents, in this case, I'd prefer something more
organized, like
--recompile=yes Force recompilation
--recompile=no Do not recompile
--recompile=check Recompile if needed (run ghc)
--recompile=default Recompile if yi.hs changed
This way there's no confusion about --recompile-option vs.
--option-recompile either. And maybe we would even have
--launch=no Don't run yi after compilation
--launch=custom Launch custom yi
--launch=in-place Don't launch custom yi (Needed? Only useful
in conjunction with --as anyway)
--launch=default (In case the default behaviour is different
from custom?)
One benefit is that you don't have to learn that --force-recompile will
launch yi, whereas --recompile won't.
Oh well, this may be over-engineering.
Kalman
--~--~---------~--~----~------------~-------~--~----~
Yi development mailing list
yi-devel@googlegroups.com
http://groups.google.com/group/yi-devel
-~----------~----~----~----~------~----~------~--~---
