If adding break&continue features to your fancy iteration syntax, I propose that any uses of these features in source code be somehow very prominent.

For example, perhaps there is a keyword that must be at the top of the fancy iteration form, something like "#:enable-continue-here-because-programmer-cannot-be-bothered-to-write-this-in-idiomatic-racket".

This prominence warns readers of the code to be on the lookout for surprise control flow (like they would on the rare occasion that they saw a "call/ec" around a loop). It also hints to newbie programmers that they are discouraged from simply transliterating syntax from other languages (rather than learning better control flow and structuring techniques).

Neil V.

<<attachment: neil.vcf>>

_________________________
  Racket Developers list:
  http://lists.racket-lang.org/dev

Reply via email to