[m-dev.] .NET back-end test results

Tyson Dowd trd at cs.mu.OZ.AU
Wed Oct 23 13:10:29 AEST 2002

On 22-Oct-2002, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> On 20-Oct-2002, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> > - lots of tests fail due to the use of C foreign clauses (FAILED.NO_CLAUSES)
> What do you think is the best way to fix these:
> 	- disable these test cases for IL grades
> 	- add C# clauses
> 	- add MC++ clauses
> 	- add Mercury clauses
> 	- support the C interface in IL grades
> 	- something else?

One of these options on a case by case basis.

If the feature is non-portable, disable test cases.
Same if it is non-essential.

If the feature can be implemented easily and/or efficiently in Mercury, do it.
That way we get it implemented in Java too.

C# clauses are preferrable to MC++ clauses - they are more readable and
are verifiable. 

C interface in IL grades is not trivial... and I doubt very much that
the C code we use could be re-used unchanged.

mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au

More information about the developers mailing list