Re: Recovering the once true meaning of type NIL in LOOP

Hi,

Sam wrote:
>Could you please also add a test case?
I had no idea how to do that short of scanning the macro-expansion, which
does not really look like a test.
As CLISP ignores types (mostly), the absence or presence of type declarations
goes without observable side-effects -- the initial value of thus declared
variables will always be NIL.

What would be interesting is output from other implementations via Pascal's clall script.

]> (loop with v = #(1 2) for x across v sum x)
Yet I was upset that such trivial examples fail while tests and sacla-tests pass.
So indeed, we need many more loop tests.

Regards,
	Jörg

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list