> Regarding the debate about whether #_XXX or xxx would be more
> approriate, to my mind the #_XXX form is winning. It has the advantage
> of making this exception condition look exceptional, both as source code
> ('not part of the code proper') and as control structure.
Well, I'm not sure that it _should_ look exceptional. After all, the
aim is presumably that people should use it because it adds to
reliability, not that people should avoid it because it makes the code
look unreadable. `#_ASSERT' scattered around is one of the few things
that could make even the most obscure stack juggling pop-11 even less
readable.
The main place that assertion would be very useful would be for
argument and result typing. Maybe a specific syntax for this would be
good.
define marmalise(em:list) -> buttie:jam;
Next on the hit parse of places to be assertive is at the top of loops
to note invarients. That could be given a syntax too.
^_^
(O O)
\_/@@\
\\~~/
~~
- RJC
|