Bill Page <bill.p...@newsynthesis.org> writes: | On Wed, Apr 1, 2009 at 11:27 PM, Gabriel Dos Reis wrote: | > | > In general, I like the abstract datatype approach taken by both | > OpenAxiom and Aldor. I would like to see critical use cases and | > sound programming styles or scalable idioms that are eased by | > exposing implementation details by exporting Rep. | > | | I am not sure I understand. Are you proposing that the Rep of a domain | should be exported or that it should *not* be exported? If it is the | latter, then I agree.
Your earlier suggestion # On the other hand, if there is no OldDomain then it is necessary to # specify the domain that will represent this new domain. We could do it # like this: # # Foo(...): with # ... # == Rep(SomeDomain) add # ... rep ... per ... reads to me that somehow the Rep of SomeDomain is exported. I'm saying I would like to see datasets that demonstrate the clear benifits of exporting the representation of a domain. If you're not proposing to export the Rep, then your proposal is a bit obscure to me. Would you mind clarifying why the above does not amount to exporting the Rep of SomeDomain? | Of course there are domains in the Axiom library | right now for which this is not true. I know of exactly one instance, and I've documented that horrible case. | I think there are some cases | where correct functioning depends on the fact that one or more domains | share the same underlying representation. The OpenAxiom compiler warns in such cases, and give suggestions. | But I believe that with a | little more programming effort these could be completely eliminated. Indeed. -- Gaby ------------------------------------------------------------------------------ _______________________________________________ open-axiom-devel mailing list open-axiom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
