Although I have a common-lisp.net account, I find that I cannot clone
the darcs repository:
darcs get rgold...@common-lisp.net:/project/iterate/darcs/iterate
Invalid repository: rgold...@common-lisp.net:/project/iterate/darcs/iterate
darcs failed: (scp) failed to fetch:
rgold...@common-lisp.net
On 1/3/12 Jan 3 -10:40 AM, Robert Goldman wrote:
> Although I have a common-lisp.net account, I find that I cannot clone
> the darcs repository:
>
> darcs get rgold...@common-lisp.net:/project/iterate/darcs/iterate
> Invalid repository: rgold...@common-lisp.net:/project/iterat
It seems that the problems were due to a version mismatch. Darcs 2.2 on
my Mac OS X box was unable to fetch the darcs repo for iterate. Darcs
2.5 was. Oddly Darcs 2.2 on Linux was able to fetch it
Cheers,
r
___
iterate-devel site list
iterate-dev
I find that ACL 8.2 gets 4 failed tests on the latest iterate from darcs:
4 out of 261 total tests failed: ITERATE.TEST::CODE-MOVEMENT.ELSE,
ITERATE.TEST::CODE-MOVEMENT.FINALLY,
ITERATE.TEST::CODE-MOVEMENT.FINALLY-PROTECTED,
ITERATE.TEST::BUG/WALK.2.
where SBCL seems to get only 1. I sa
On 1/4/12 Jan 4 -8:22 PM, Robert Goldman wrote:
> I find that ACL 8.2 gets 4 failed tests on the latest iterate from darcs:
...snip...
> Looking further, I think I have identified the divergence --- in ACL,
> CL:RETURN is a special-operator, and in SBCL, it is not:
>
> All
Steve Haflich from Franz kindly clarified to me my misunderstanding of
special-operators and macros.
In particular, he pointed out to me that implementations are free to
implement special operators as macros. Steve writes:
"I assure you that the set of special operators in ACL is _fixed+, and
th
Is this mailing list (and the iterate library) still active?
I made some patches to iterate to address issues on ACL, but I don't
believe that they are moving forward to incorporation in the library.
The last email on this list that seems to show anything like forward
motion (and that's debatable
On 5/7/12 May 7 -10:09 AM, Vladimir Sedach wrote:
> I think the problem is that Attila does not read iterate-devel. There
> are quite a lot of patches and bug reports submitted here in the past
> 2 years that haven't made it into the code.
>
> I've CC'ed Attila. I guess another question would be i
On 5/9/12 May 9 -5:50 PM, Attila Lendvai wrote:
>> Perhaps it would be a good thing to give some additional people the
>> commit bit; I am not sure if anyone other than Attila is currently
>> active (apologies if I am wrong about that).
>
> i'm "active", and reading the list every once in a while,
On 5/11/12 May 11 -12:58 PM, Attila Lendvai wrote:
>> Would you consider getting someone else into the group, then? I am not
>> really in a position to volunteer for much upkeep right now, but perhaps
>> could help scrounge someone up.
>
> well, this decision is in no way my responsibility, or is
I was just testing out the version of ITERATE with Ilya's new fixes.
Question: what do we expect to happen when `ASDF:TEST-SYSTEM` is run on
iterate? I see 8 test failures, on ACL 10.1, as follows:
```
8 out of 267 total tests failed: ITERATE.TEST::ALWAYS.FINALLY,
ITERATE.TEST::NEVER.FINAL
On 24 Jan 2018, at 15:09, Robert Goldman wrote:
I was just testing out the version of ITERATE with Ilya's new fixes.
Question: what do we expect to happen when `ASDF:TEST-SYSTEM` is run
on iterate? I see 8 test failures, on ACL 10.1, as follows:
```
8 out of 267 total tests f
On 24 Jan 2018, at 15:39, Ilya Perminov wrote:
Hi Robert,
To "revert" my patch manually just revert this change:
--- old-iterate/iterate.lisp2018-01-15 16:49:24.171636397 -0800
+++ new-iterate/iterate.lisp2018-01-15 16:49:24.171636397 -0800
@@ -3374,7 +3374,7 @@
(if (not (and (int
Sorry -- I got the markdown all stuffed up in my last message. I think
it's readable, though.
Best,
r
On 24 Jan 2018, at 15:58, Robert Goldman wrote:
On 24 Jan 2018, at 15:39, Ilya Perminov wrote:
Hi Robert,
To "revert" my patch manually just revert this change:
On 24 Jan 2018, at 16:17, Ilya Perminov wrote:
I think the warings are expected. A note just above them says "Note:
These tests generate warnings involving MACROLET within Iterate".
I am not sure why our test results are different. Maybe my SBCL
version is too old, I'll try the latest one.
On 24 Jan 2018, at 16:17, Ilya Perminov wrote:
I think the warings are expected. A note just above them says "Note:
These tests generate warnings involving MACROLET within Iterate".
I am not sure why our test results are different. Maybe my SBCL
version is too old, I'll try the latest one.
On 24 Jan 2018, at 16:55, Ilya Perminov wrote:
The latest SBCL (1.4.3) on Linux gives 2 failues:
ITERATE.TEST::BUG/WALK.2 and ITERATE.TEST::BUG/COLLECT-AT-BEGINNING.
Hm. According to Attila, you should have 5 failures (which is what I
have):
```
5 out of 268 total tests failed: ITERATE.TE
the iterate-tests system.
https://common-lisp.net/project/cl-test-grid/library/iterate.html
-- Patrick
On Jan 24, 2018, at 4:38 PM, Robert Goldman
wrote:
On 24 Jan 2018, at 16:17, Ilya Perminov wrote:
I think the warings are expected. A note just above them says "Note:
These tests gen
On 24 Jan 2018, at 17:37, Ilya Perminov wrote:
My iterate directory was missing some patches. With the latest version
from darcs 5 tests fail:
5 out of 268 total tests failed: ITERATE.TEST::ALWAYS.FINALLY,
ITERATE.TEST::NEVER.FINALLY, ITERATE.TEST::THEREIS.FINALLY,
ITERATE.TEST::BUG/WALK
On 24 Jan 2018, at 18:06, Attila Lendvai wrote:
My iterate directory was missing some patches. With the latest
version from
darcs 5 tests fail:
5 out of 268 total tests failed: ITERATE.TEST::ALWAYS.FINALLY,
ITERATE.TEST::NEVER.FINALLY, ITERATE.TEST::THEREIS.FINALLY,
ITERATE.TEST::BUG/WAL
It looks like we just need to make a tarball, right? And we should put
the :version metadata in iterate.asd.
I don't think there's anything more that needs to be done, do you?
I'm not in the iterate group on cl.net, so I can't do it myself.
Best,
R
On 6 Feb 2018, at 17:19, Attila Lendvai w
I was going to define an `AVERAGING` collector clause for iterate, but
I'm not sure how to do it. The obvious thing, it seemed to me, would be
to sum the values as I go along, and count them, and then divide the sum
by the count when leaving the loop.
But the examples for `DEFMACRO-CLAUSE` in
;; convert our sample to a list, but only if we
actually took the sample
(when (plusp ,i)
(setf ,sample
(iter (for ,row in-vector ,buffer)
(until (eq ,row ',sigil))
(collect ,row)))))
Cheers,
Russ Tyndall
Accelerat
(IF (PLUSP #:CNT4007)
(/ #:SUM4008 #:CNT4007)
0))
(RETURN MEAN)))
NIL))
Cheers,
Russ Tyndall
Acceleration.net
- Original Message -
From: Robert Goldman [mailto:rpgold...@sift.info]
To: r...@acceleration.net
Cc: iterate-devel@common-lisp.net
Sent: Tue, 1
I was thinking we could tag the current master as 1.6.0 and call it a
release. I hate to leave people -- especially people who get their copy
of iterate from quicklisp -- stuck using a version of iterate that has
known bugs for which a fix has been committed.
I would bump the current version
I have been trying to repair the GitLab CI, and I'm stuck on clasp.
Whatever I try to do with clasp docker images -- and I've tried the
clfoundation ones, the clasp-devel ones and even made one myself -- I
get an error in the GitLab pipeline trying to start up the image. For
example:
```
Us
On 15 Dec 2022, at 5:18, Luís Oliveira wrote:
> On Wed, 14 Dec 2022 at 22:10, Robert Goldman wrote:
>> I have tried firing up this image myself and then running make test l=clasp
>> in it, and the test works fine. So it's something about the interaction
>> between t
27 matches
Mail list logo
