Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| > Not bad design; bad symbol wording. I'll fix the `in symbol' part of
| > the documentations.
|
| OK.
|
| > | And the above
| > | specification for CoercibleFrom additionally introduces
| > | interdependencies.
|
| > No. CoercibleFrom turns naked
| > coerce: S -> %
| > into standalone category. That is all folks.
|
| If you say so.
|
| > | >> A has HomotopicTo B iff
| > | >> A has CoercibleTo B and A has CoercibleFrom B
|
| That here is not much better...
I hope it is just my mailer which did not show your suggested improvement.
| ++ A is homotopic to B iff any element of domain B can be
| ++ automically converted into an element of domain B, and nay
| ++ element of domain B can be automatically converted into an A.
| HomotopicTo(S: Type): Category == Join(CoercibleTo S, CoercibleFrom S)
|
| After I have added
|
| MyInt: HomotopicTo(Integer) == add ...
which brings:
coerce: MyInt -> Integer
coerce: Integer -> MyInt
| on *top* of the OpenAxiom library (i.e. without modifying the OA-lib),
| then for A=Integer and B=MyInt the right hand side of the 'iff' above
| is true. Should I expect that
|
| Integer has HomotopicTo MyInt
|
| gives true?
Is that what the documentation says?
| I better don't repeat the 'interdependency' stuff.
Indeed.
-- Gaby
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
open-axiom-devel mailing list
open-axiom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
