Subject: Mathemagix
List archive
- From: Joris van der Hoeven <address@concealed>
- To: <address@concealed>
- Cc: <address@concealed>, <address@concealed>
- Subject: Roadmap for Mathemagix
- Date: Fri, 25 Jun 2004 17:00:56 +0200 (CEST)
Hi once again,
Just to give some further information about how I will spend
the (little) time I have for working on Mathemagix:
1) Complete the language:
a) Implicit type conversions
b) Generic types
c) New type/module declarations
d) Exceptions
e) Syntactic sugar
f) Symbolic types
In the meanwhile, I hope that volunteers will write bindings
for most of the libraries mentioned in my previous message.
Some discussions are probably necessary for (f) and maybe (e).
2) Rewrite the type system. Currently, the type system works
well for most things one usually does in C++, but the more
innovative features like propagation of ambiguity are still
a bit buggy. A complete rewriting of the type system should
fix these problems.
In the meantime, if you ever have problems with function calls
which should work but which lead to type mismatch errors,
then a small amount of casting usually fixes the problem.
The worst current example is the code
i:Integer := 1;
j:Integer := 2;
i := j;
in which the last assignment should be changed into
i := j :> Integer;
The reason is that j actually has the type Alias Integer.
For the time being, one should also be careful not to
abuse overloading.
Some further points which are being worked on at the moment are
an emacs-mode and a protocol for how to convert between similar
types from extern libraries.
Best wishes, Joris
- Writing bindings for C++ (template) libraries in Mathemagix, Joris van der Hoeven, 06/25/2004
- Roadmap for Mathemagix, Joris van der Hoeven, 06/25/2004
Archive powered by MHonArc 2.6.18.