[m-dev.] standard trailing library

Julien Fischer juliensf at csse.unimelb.edu.au
Wed Apr 9 18:14:23 AEST 2008

On Wed, 9 Apr 2008, Zoltan Somogyi wrote:

> On 09-Apr-2008, Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
>> (1) add it to the standard library and make all the operations
>>     throw an exception or abort in non-trailing grades.
>> (2) add a standard trailing library, e.g. std_tr, which is only
>>     compiled and installed in trailing grades.
>> What are people's preferences?  (Mine is for 2).
> You cannot do (2) alone, because you cannot prevent someone from compiling
> the module in a non-trailing grade, 
> even if it is not so compiled by default.

Yes I can.

 	:- pragma require_feature_set([trailing]).

> The choice seems to be between both (1) and (2), and (1) alone.
> I have an aesthetic preference for (1)+(2), but it will need more work
> on the install system than just (1). If I were you, I would do (1) right now,
> and add (2) when your todo list has no more urgent items.

I'm not sure that it requires that much work on the install system (it's
work that is probably worth doing anyway as it will be useful elsewhere,
e.g. not compiling the trace directory in hlc grades.)

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

More information about the developers mailing list