[m-rev.] for review: change java packaging

[Julien Fischer]

On Wed, 17 Jun 2009, Peter Wang wrote:

> jmercury sounds ok to me, but it's easy to change.

jmercury is fine by me.

> Branches: main
>
> Put all Mercury-generated Java classes into the package `jmercury' and
> runtime classes into `jmercury.runtime'.  The Mercury module hierarchy is
> not reflected in the package name.  We name sub-module classes using
> their fully-qualified module names with `__' between components, e.g.
> `bit_buffer.read' produces `class bit_buffer__read'.
>
> As all generated Java code is in the same package we don't need to package
> qualify identifiers, and we don't need the hack to avoid clashing package
> and class names.  It also makes it easier to write Java foreign code because
> generated Java class names are easier to predict from Mercury module names.
>
> The package names are not `mercury' and `mercury.runtime' because on
> case-insensitive file systems we may end up with a `mercury' directory
> that could be confused with the `Mercury' directory.

...

That's fine.

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