[m-rev.] trivial diff: delete java mercury directories

[Paul Bone]

On Tue, Jun 16, 2009 at 03:09:25PM +1000, Peter Wang wrote:
> 2009/6/16 Zoltan Somogyi <zs at csse.unimelb.edu.au>:
> >
> >> I suppose that means I should go ahead and delete Mmake support for Java, which
> >> is the only way a "mercury" directory can appear at the same level as a
> >> "Mercury" directory.
> >
> > I think that would be throwing the baby out with the bathwater.
> 
> I also forgot about implict make rules.  Even if it's not officially
> supported, Mmake still gets quite far into the process and you end up with
> the `mercury' directory.
> 
> Ok, let's package everything in au.edu.unimelb.mercury.
> 
> I think we can use a different mapping from Mercury module names to Java
> package/class names.  A simpler scheme would be to put everything in
> package `au.edu.unimelb.mercury', then
> 
>     module `foo' goes to `foo.java'
>     module `foo.bar' goes to `foo__bar.java'
>     etc.
> 
> Since all Mercury code is in the same package, we don't need to fully
> qualify everything with au.edu.unimelb.mercury.  I don't know why I didn't
> think of it before.
> 

I don't think third party code should begin with this prefix.  It is
written in mercury not by the mercury group.

If two projects both calling themselves 'x' create code and it gets
placed in au.edu.unimelb.mercury.x there may be problems.  If instead
they are built with their own domain names as prefixes they will be
named apart.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 489 bytes
Desc: Digital signature
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20090616/25e503d1/attachment.sig>