Hi...
On Feb 20, 2008 9:50 AM, Paul Bone <[EMAIL PROTECTED]> wrote:
> Mercury also supports 'grades', this makes it different to other
> compliers and more interesting to package. Each grade represents a
> complier backend and some options. There are two C backends, a Java
> backend, and Erlang backend and a MSIL backend. Options can include
> optional garbage collection (as apposed to never reclaiming memory),
> profiling support, debugging support and more.
>
> I'd like to package the library and runtime for each grade. These can
> all be installed concurrently and won't conflict.
There are at least two issues you may have to deal with here:
* Mercury does not provide any guarantees about a stable library ABI,
so you'll have difficulty packaging grades using shared libraries and
not breaking applications when you update the libraries.
* Mercury standard libraries can be very large (tens of megabytes in
some of the debug grades), so packaging every possible grade seems
rather wasteful of archive space. If you ask me, you need to pick a
small set of useful grades which cover most use cases. I'm not sure
how many architectures Debain supports at the moment, but if you
aren't careful you could easily consume hundreds of megabytes of
fileserver space just on Mercury library grades (10+ architectures *
10s of Mb/grade * many grades).
Peter
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
