Hey Beneroth,
Thanks for the kind words, my pleasure to share with you all.
Of course you can also use (or) to achieve the opposite - stop when a call
> or evaluation returns something (not NIL).
> This way you have actually a very cheap implementation of the Design
> Pattern (GoF) 'chain of resp
Of course you can also use (or) to achieve the opposite - stop when a call or
evaluation returns something (not NIL).
This way you have actually a very cheap implementation of the Design Pattern
(GoF) 'chain of responsibility', when one function successfully handles the
required case, stop there
Hi Erik
Thanks for writing this awesome article, your humour made it a very joyful read!
I actually found that technique myself too, and used it in certain cases, its
just perfect when you have multiple sequential things to do but you want to
cancel execution when one of it fails.
When using th
