[m-dev.] [m-users.] Closed source Mercury projects on Windows

Julien Fischer jfischer at opturion.com
Fri Jun 8 16:31:11 AEST 2018

On Thu, 7 Jun 2018, Zoltan Somogyi wrote:

> On Thu, 7 Jun 2018 23:21:02 +1000 (AEST), Julien Fischer <jfischer at opturion.com> wrote:
>>> +In the following, "Mercury Core Libraries" refers to all source
>>> +code in the following directories of this distribution:
>>> +
>>> +    browser, java/runtime, library, mdbcomp, runtime, trace
>>> +
>>> +(No other part of this distribution is automatically linked into an
>>> +executable program by the Mercury system.)
>> The ssdb library is also automatically linked into programs.
> Are ssdb grades ready for use, and are they publicly documented?

Mostly not; they are however the only version of the debugger that
supports the non-C backends.

> If not, there is no particular hurry, though it would be nice to fix its license
> now, rather than later.

>> The rest of your change looks fine; a couple of other things:
>> 1. library/test_bitset.m is included in the library and is GPL licensed
>> according to the header comment.  (I know it's just test code, but it
>> is included in there.)
> It seems I am the only who has ever committed anything to test_bitset.m
> either in its original location in the compiler directory or its current location
> in the library, so I can give permission to change it to COPYING.LIB.

I wasn't expecting it to be a problem ;-)  (I just grepped the affected
directory for "GNU General".)


More information about the developers mailing list