Re: edebug specs for cl-loop

[Thierry Volpiatto <thierry.volpiatto@gmail.com>]

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>> loop understand this but not edebug: (Note where the for rand2 line is now)
>
>>         for alphaindex = (random* (length alph))
>>         collect rand1 into ls
>>         for rand2 = (aref alph alphaindex)
>>         collect rand2 into ls
>
> By "edebug" which edebug-spec do you mean: the simple default (&rest &or
> symbolp form) or the complex one?  AFAICT, the simple default should
> handle the above just fine, right?
I don't understand what you call simple default and complex one.

Assume the edebug specs in cl-macs (the ones commented) are loaded,
otherwise all this is irrelevant because edebug doesn't work at all in
loop.

I mean that on the above form, if I do C-M-x on it the function is
evaluated with no errors, and if I do C-u C-M-x I have an error:

--8<---------------cut here---------------start------------->8---
edebug-syntax-error: Invalid read syntax: "Failed matching", ([&optional ["named" symbolp]] [&rest &or ["repeat" form] loop-for-as loop-with loop-initial-final] [&rest loop-clause])
--8<---------------cut here---------------end--------------->8---

>> loop understand this but not edebug: (note where the while line is now)
>
>>           with len = (length (window-list))
>>           for count from 1
>>           while (< count len)
>>           for w1 = (iter-next wlist)
>>           for b1 = (window-buffer w1)
>>           for s1 = (window-start w1)
>>           for w2 = (iter-next wlist)
>>           for b2 = (window-buffer w2)
>>           for s2 = (window-start w2)
>           
>> Both give same result.
>
> Here as well, the simple default spec should handle this just fine.
Here both C-M-x and C-u C-M-x works.


-- 
  Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997