Ralf Hemmecke wrote:
>
> > Yes, Spad is irregular here: if '=>' is last in the block, it
> > effectively is executed in surrouding block.
>
> Sorry, but I don't like that. That is effectively one more rule for a
> programmer to learn SPAD. And it is unnecessary (IMHO).
...
> Also look at the attached programs. The spad and the aldor version
> output the same.
Sorry I was wrong in my explanation. The real thing is simple:
'if' does not create a new block. In Spad you need at two
instructions in sequence to get a block, so lone '=>' after
'if' is considered part of the same block as instructions
around 'if'. Once you have two of more instructions in 'then'
or 'else' part they form new block and '=>' leaves this block.
This is less useful than what I initially thought.
--
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.
