What would you prefer? Maybe "mirror-analysis"? Or "readable-analysis"?

Also, instead of modifying "output-relations", how about modifying compile
so that it respects the mirroring flag? That way, existing code that uses
"output-relations" will work without modification, and the mirroring option
will apply to all operations that modify the analysis cache?




On Sun, Jan 6, 2013 at 6:23 PM, Peter Vlugter <notifications@github.com>wrote:

> In src/main/scala/com/typesafe/zinc/Settings.scala:
>
> > @@ -158,6 +159,8 @@ object Settings {
> >      file(    "-analysis-cache", "file",      "Cache file for compile analysis",            (s: Settings, f: File) => s.copy(analysis = s.analysis.copy(cache = Some(f)))),
> >      fileMap( "-analysis-map",                "Upstream analysis mapping (file:file,...)",  (s: Settings, m: Map[File, File]) => s.copy(analysis = s.analysis.copy(cacheMap = m))),
> >      boolean( "-force-clean",                 "Force clean classes on empty analysis",      (s: Settings) => s.copy(analysis = s.analysis.copy(forceClean = true))),
> > +    boolean("-mirror-cache-as-text",  "Store a side-mirror of the analysis cache as readable text",
>
> Better (shorter) option name possible? Could also modify the
> output-relations option to output the relations file alongside all analysis
> cache files (so covering both options).
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/typesafehub/zinc/pull/24/files#r2560907>.
>
>



-- 
Mark Craig Chu-Carroll
*** Software Engineer@foursquare, Software Tools/Programming Language/Math
Geek
*** Email: markcc@foursquare.com <markcc@gmail.com>; Twitter: @MarkCC
*** Blog: http://scientopia.org/blogs/goodmath