[imp-hackers] LOOP non-compliance

[Stas Boukarev]

Juan Jose Garcia-Ripoll <juanjose.garciaripoll at googlemail.com> writes:

> This is probably a silent cry in the woods and nobody will listen, but
> could other implementations please warn users that there is a precise order
> of statements in LOOP?
>
> http://www.lispworks.com/documentation/HyperSpec/Body/m_loop.htm
>
> There are a lot of libraries out there which are being developed by
> implementations that do not care whether (LOOP WHILE ... FOR I = ...) is a
> valid or not, and this is at least affecting users of one implementation
> that does (ECL).
I wish the opposite was true (standard or not), that all implementations
accepted (loop while ... for ..), it's such a pain to write LOOPs without this
construct.

-- 
With best regards, Stas.