[m-rev.] for review: move analysis framework into compiler

Peter Wang novalazy at gmail.com
Tue Feb 19 12:37:05 AEDT 2008

On 2008-02-18, Zoltan Somogyi <zs at csse.unimelb.edu.au> wrote:
> On 17-Feb-2008, Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
> >> compiler/notes/coding_standards.html:
> >> 	Remove references to analysis directory and libmer_analysis.
> >>
> >> I would prefer the analysis*.m files to retain their history across the
> >> move, but it's not critical.
> >
> > Did you consider leaving them in the present location and either using
> > mmc -f, or just copying them across to the compiler directory at
> > compile time?
> I don't think either of those approaches would work. However, you don't want
> to lose the history either.
> I think the analysis directory should be left in place but unreferenced,
> and the files in it should also be left in CVS but should have their contents
> replaced with a comment to the effect that the files are now in the compiler
> directory. We have done this before; see compiler/inst.m.

Ok.  I think I will leave these files as-is:

    .cvsignore .mgnuc_copts .mgnuc_opts .nocopyright ANALYSIS_FLAGS.in

These files would be replaced by stubs:

    Mercury.options Mmakefile analysis.file.m analysis.m mer_analysis.m


mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au

More information about the reviews mailing list