From: Florian Zumbiehl fl...@florz.de
Subject: Re: [Chicken-hackers] [PATCH 1/2] tcp: disable interrupts
Date: Mon, 18 Mar 2013 11:50:46 +0100
Hi,
On Mar 17, 2013, at 1:58 AM, Florian Zumbiehl wrote:
If you cannot be sufficiently sure
that your approach is correct to be willing to
From: John Cowan co...@mercury.ccil.org
Subject: Re: [Chicken-hackers] [PATCH] non-termination with (declare (inline
...))
Date: Sun, 17 Mar 2013 18:41:10 -0400
Felix scripsit:
This leaves the decision to inline to the compiler
Excellent. However, I hope that notinline forces the
On Mar 18, 2013, at 11:22 AM, Felix wrote:
From: Jim Ursetto zbignie...@gmail.com
Subject: Re: [Chicken-hackers] [PATCH] non-termination with (declare (inline
...))
Date: Mon, 18 Mar 2013 10:57:49 -0500
Is that just for declare or does it also apply to define-inline?
No, define-inline
Hi Felix,
On Mon, 18 Mar 2013 11:25:02 -0400 (EDT) Felix
fe...@call-with-current-continuation.org wrote:
From: Mario Domenech Goulart mario.goul...@gmail.com
Subject: Re: [Chicken-hackers] [PATCH 3/4] Remove ##sys#expand-home-path.
Date: Mon, 18 Mar 2013 10:33:49 -0400
Making robust
Hi,
If we keep the ~-expansion, any safe code that use the filesystem API
will have to resort to tricks like
(operation (if (absolute-pathname? the-path)
the-path
(make-pathname (current-directory) the-path)))
to guard against input that would cause
Here's a full patch to avoid context switches screwing up the error message
reported to the user, and also consolidates much of the error handling.
I think this patch is sufficient because the only actual issue, as I understand
it, is that under high load you will occasionally get an incorrect
Mario Domenech Goulart scripsit:
$ mkdir '~'
While this is certainly Posix-legal, my opinion is that anyone who does
it deserves to lose. In the Real World, Posix systems often have portions
of the filesystem that are not fully Posix-compliant.
--
In politics, obedience and support
Hi John,
On Mon, 18 Mar 2013 16:01:24 -0400 John Cowan co...@mercury.ccil.org wrote:
Mario Domenech Goulart scripsit:
$ mkdir '~'
While this is certainly Posix-legal, my opinion is that anyone who does
it deserves to lose.
Indeed, but the actual point is that a malicious user can create
On Mon, Mar 18, 2013 at 02:03:41PM -0400, Mario Domenech Goulart wrote:
Maybe I'm too paranoid? Or missing something?
No, you're spot on. I think given a choice, we should always err on
the side of security and adhere to the Principle Of Least Astonishment.
For convenient scripting, a dwim
From: Mario Domenech Goulart mario.goul...@gmail.com
Subject: Re: [Chicken-hackers] [PATCH 3/4] Remove ##sys#expand-home-path.
Date: Mon, 18 Mar 2013 13:02:01 -0400
Hi Matt,
On Mon, 18 Mar 2013 08:45:17 -0700 Matt Welland m...@kiatoa.com wrote:
Please please keep the expansion of ~.
From: Jim Ursetto zbignie...@gmail.com
Subject: [PATCH] Avoid context switch during TCP errno reporting
Date: Mon, 18 Mar 2013 14:06:03 -0500
Here's a full patch to avoid context switches screwing up the error message
reported to the user, and also consolidates much of the error handling.
I
Hello!
The symbolgc-test was failing for me again. As this test is somewhat
nasty and since I can't provide a fix, I have modified runtests.sh to
continue, regardless of the exit-status of the symbolgc-test program.
cheers,
felix
___
Chicken-hackers
On Mon, Mar 18, 2013 at 10:05:46PM +0100, Felix wrote:
I disagree. We can still try to make the core system practical,
instead of a mindless API server for low-level facilities wrapped in
s-expression syntax.
Nobody's arguing for that. Abstraction (the right kind!) is what makes
Scheme so
On Mar 18, 2013, at 4:17 PM, Felix wrote:
From: Jim Ursetto zbignie...@gmail.com
Here's a full patch to avoid context switches screwing up the error message
reported to the user, and also consolidates much of the error handling.
Applied. Thanks.
Argh! I made an error in the patch. I've
14 matches
Mail list logo
