Ralf Hemmecke wrote:
>
> > But there is a bunch of issues reported.
>
> Obviously almost nobody uses the SF bugtracker.
> http://sourceforge.net/p/fricas/bugs/
>
> :-(
>
> I think we should encourage to use it more often.
> So, which issues do you mean? Something where I can help?
Nr 36 in SF bugtracker got fixed few days ago. It would be
good to do something about nr 37 (ideally we should implement
approximate gcd, minimaly fuzzy version of 'exquo', so that
when gcd decides thet there is common factor 'exquo' should
succeed).
Krystian reported few weird behavoiurs from Spad compiler...
HyperDoc may crash when showing operations from complex
types (more precisely, when type has complex parameters).
Then, there is issue of ')nopile' mode. It is easy to allow
extra semicolons. Current semantics of semicolon is to throw
away computend value, clear but seems useless (except for
signaling error when there are too many semicolons). We
can change this to no-op. Other thing is that semicolons
should be optional after brace. If we allow extra semicolons,
then we may get away with essentially inserting extra
semicolon after closing brace. However still there is
question about:
if b1 then if b2 then {do1}; else {do2}
Namely, with which 'if' has 'else'? Typical sysntax
is that above 'else' goes with second 'if'. But
given that naively inserting semicolons after closing
brace would break
if b1 then if b2 then {do1} else {do2}
where 'else' should go to first 'if'.
--
Waldek Hebisch
[email protected]
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.
