[mercury-users] .NET Mercury type representation.

[Wendelin Reich]

Dear Peter,

The generic representation of arbitrary Mercury types under .NET to
which you refer seems straightforward - I wouldn't know how you could
improve that. With "inefficient" I meant the ergonomics rather than the
data modeling... in C#, you probably wouldn't want to access members in
a (long) list through recursive demodulation. So, you would end up
writing long, difficult to read statements for accessing data in complex
objects.

Thinking about it, this seems to a .NET "problem" rather than a problem
of the Mercury back-end... Mercury's type system is just too flexible
for languages like C#, isn't it? But since arrays are already mapped so
nicely to .NET, this mustn't be a problem. In my own code, I use
whatever abstract data types mercury has to offer and convert them to
arrays before I hand it back to C#.

Cheers, Wendelin

--------------------------------------------------------------------------
mercury-users mailing list
post:  mercury-users at cs.mu.oz.au
administrative address: owner-mercury-users at cs.mu.oz.au
unsubscribe: Address: mercury-users-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-users-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------