Martin Rubey wrote:
> Waldek Hebisch <[email protected]> writes:
>
> > Create a file like:
...
> > and compile it.
>
> shoul be an input file, analogous to bugs2008-ExportType.spad, and a
> test in bugs2009, I guess?
>
IHMO compiler test should be organized differently. However,
ATM our main test is algebra source, so there is little
need for extra test (the case above is a rare exception).
> > variables). For example:
> >
> > bar(x : Type) : Integer ==
> > x is Integer => 1
> > 0
> >
> > Note: currently it is not possible to use such functions from
> > interpreter, they only work in Spad code.
>
> both should also be tested (in i-bugs2009 and bugs2009), I'd say...
>
The construct is used in algebra, so test would be a duplicate.
Concerning interpreter: I do not think we should test for
uniplemented features to the testsuite. Such tests would just
add useless noise. Proper place for such test is in bug
database, more precisely in SourceForge database (because
extracting tests from wiki is unreliable (in wiki it is too
easy to alter or delete tests) and tedious).
--
Waldek Hebisch
[email protected]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/fricas-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
