Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| > In OpenAxiom-1.2.0, you can use { } to construct sets directly.
|
| Gaby,
|
| I don't know whether you want to make SPAD syntax more similar to Aldor,
I'd, like as much as possible, to retain good aspects of Axiom as
originally by defined Jenks&Sutor while expanding it to solve harder
problems and taking advantages of recent advances in system design and
implementations.
| but in case Integer and Set(Integer) are the only things in scope, what
| should
|
| a := {1}
|
| stand for?
Well, I was talking about the interpreter where that is not an issue:
domains are loaded automatically on demand (assuming they are
exposed, which is the case for List and Integer).
I expect the interpreter to take more central role than the compiler.
The interpreter is what most OpenAxiom users `see'.
To answer the above question for the compiler, the above is invokation
of brace operator with an integer operand, therefore it should resolve
to whatever is in scope -- otherwise error. It contains no syntactic
element that indicates that the braces are used to group statements.
|
| Would the compiler complain because of ambiguities or what type would
| 'a' have?
|
| If braces are allowed to enclose blocks of code (like in Aldor), I don't
| think the set construction with braces is a good idea.
Blocks of codes are separated by semicolons. Set elements are
separated by comma. I'm not sure why you think this is a problem.
Could you elaborate with *typical* examples?
I must also confess that I'm not a big fan of losing braces for block
of codes, when we have already many ways of writting blocks of codes
-- and I'm not sure I've seen, in the context of Axiom, contexts where
delimiting blocks of codes by braces is structurally superior to the
layout rule. Yes, you have to count what you don't see, but that is
not going to go away.
|
| Just my 2 cents.
Your feedback is always appreciated.
-- Gaby
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
open-axiom-devel mailing list
open-axiom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
