FWIW, I've run the cl-test-grid tests (testsuites of 56 libraries, and
compilation/loading of all
the ASDF systems found in Quicklisp). No regressions comparing to ECL 91356f2d.
21.09.2012, 01:12, "Juan Jose Garcia-Ripoll" :
> This is was latest commitcommit ce653d889d818ba8b6709812a83d324676203
On Mon, 24 Sep 2012 22:26:27 +0200
Juan Jose Garcia-Ripoll wrote:
> On Fri, Sep 21, 2012 at 12:11 AM, Matthew Mondor
> wrote:
>
> > I noticed that functions such as WRITE-SEQUENCE will signal a condition
> > of type SIMPLE-ERROR if EPIPE is returned when writing.
>
>
> I just checked: it canno
On 25/09/2012, at 5:29 AM, Juan Jose Garcia-Ripoll wrote:
> On Mon, Sep 24, 2012 at 9:21 PM, Juan Jose Garcia-Ripoll
> wrote:
> I do not see the problem with this patch:
>
> I now see what you mean. There are a couple of mistakes in the routines that
> store and retrieve the errors. I have ma
On Mon, 24 Sep 2012 22:26:27 +0200
Juan Jose Garcia-Ripoll wrote:
> I just checked: it cannot be WRITE-SEQUENCE that signals the error, but the
> file operations. This definitely could be fixed. Do you have a simple
> reproducible example so that I can trace the chain of functions that
> provokes
On Mon, 24 Sep 2012 22:26:27 +0200
Juan Jose Garcia-Ripoll wrote:
> On Fri, Sep 21, 2012 at 12:11 AM, Matthew Mondor
> wrote:
>
> > I noticed that functions such as WRITE-SEQUENCE will signal a condition
> > of type SIMPLE-ERROR if EPIPE is returned when writing.
>
>
> I just checked: it canno
On Mon, 24 Sep 2012 22:23:31 +0200
Juan Jose Garcia-Ripoll wrote:
> I would say no ERRNO is needed, provided we have the appropriate error
> hierarchy. Right now ECL does not return ERRNO in any of the errors
> generated by the C library. To be fair, the errno would be rather useless
> unless we
On Fri, Sep 21, 2012 at 12:11 AM, Matthew Mondor
wrote:
> I noticed that functions such as WRITE-SEQUENCE will signal a condition
> of type SIMPLE-ERROR if EPIPE is returned when writing.
I just checked: it cannot be WRITE-SEQUENCE that signals the error, but the
file operations. This definitely
On Fri, Sep 21, 2012 at 12:11 AM, Matthew Mondor
wrote:
> I noticed that functions such as WRITE-SEQUENCE will signal a condition
> of type SIMPLE-ERROR if EPIPE is returned when writing. This is
> admitedly in non-standard territory, as only TYPE-ERROR is specified
> for WRITE-SEQUENCE.
>
> I co
On Fri, Sep 21, 2012 at 9:53 PM, Juan Jose Garcia-Ripoll <
juanjose.garciarip...@gmail.com> wrote:
> I cannot reproduce the flexi-streams problem, but I can reproduce the
> usockets one.
>
One error has been fixed: weak hashes sometimes returned the wrong value or
used an uninitialized field. The
On Mon, Sep 24, 2012 at 9:21 PM, Juan Jose Garcia-Ripoll <
juanjose.garciarip...@gmail.com> wrote:
> I do not see the problem with this patch:
>
I now see what you mean. There are a couple of mistakes in the routines
that store and retrieve the errors. I have made some simplifications and
will up
On Wed, Aug 29, 2012 at 1:20 PM, Mark Cox wrote:
> The issue relevant to ECL is that commit 469c8a5 introduces a problem that
> results in one of the following errors:
I do not see the problem with this patch:
commit 469c8a520f8e3a053775597f4d82a32e656161bf
Author: Juan Jose Garcia Ripoll
Dat
11 matches
Mail list logo