Hello,

I've just checked in a few additional test lines that seem to suggest 
that cycle index series already work fine in the species context, only 
that the way we call the test (function "check") causes the compiler to 
do something strange.

There are serveral things now.

1) Why does this check only fail for compose$CycleIndexSeries but not 
for any of the other operations (+ and * from CycleIndexSeries or 
compose from ExponentialGeneratingSeries)?
The only reason why compose is different is that it is implemented 
directly in the domain CycleIndexSeries and thus overrides 
compose$FormalPowerSeries(...).

2) I actually don't want to change the parameters of the "check" 
function from

check(S: (L: LabelType) -> CombinatorialSpecies L, ...): () == {...}

to (for example)

check(S: CombinatorialSpecies Integer, ...): () == {...}

not that the change would be difficult, but the original form would be 
needed anyway for an implementation of a species algebra. I would then 
rather like to work with species as functions (thus forgetting the 
parameter L) instead of always giving an explicit L. And actually, I 
must, because of the whole design of AC.

Any ideas to change something in AC, but *not* the "check" function in 
test/species.as.nw?

Ralf

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aldor-combinat-devel mailing list
Aldor-combinat-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aldor-combinat-devel

Reply via email to