On Sun, Aug 17, 2008 at 4:05 PM, Jörg F. Wittenberger
[EMAIL PROTECTED] wrote:
too bad. Once again a fix for the fix.
This time I overlooked a now superflous assignment.
##sys#standard-{in,out}put are already handled specially (and
stored in the thread-state), so this doesn't make things any
Am Dienstag, den 19.08.2008, 08:59 +0200 schrieb felix winkelmann:
On Sun, Aug 17, 2008 at 4:05 PM, Jörg F. Wittenberger
[EMAIL PROTECTED] wrote:
too bad. Once again a fix for the fix.
This time I overlooked a now superflous assignment.
##sys#standard-{in,out}put are already handled
Am Montag, den 18.08.2008, 18:24 +0200 schrieb Tobia Conforto:
Jörg F. Wittenberger wrote:
There are several timeout, counter and other parameters - within
chicken and elsewhere in my program - if I want to set them from a
remote-repl, which presumably runs in it's own thread
Am Montag, den 18.08.2008, 09:19 -0700 schrieb Elf:
On Mon, 18 Aug 2008, Jörg F. Wittenberger wrote:
Hi Elf,
first of all: sorry about not having had the time to read your egg but
anyway asking questions about it.
please read the docs in the future, as this issue is addressed.
I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Aug 2008, at 10:27 am, Jörg F. Wittenberger wrote:
That's what I have been able to do bevor. That's not the aim. I need
to change all timeouts for all thread which are started after the
change.
This boils down to an interesting question:
2008/8/18 Elf [EMAIL PROTECTED]:
#; is a very special sort of case. it would be a minimum of several lines
to perform syntax highlighting correctly with it.
give me a full list of whats missing from vim, and ill look at it. i dont
use vim, but i do use vi :)
-elf
The missing things I
Alaric Snell-Pym wrote:
Normal production configuration changes should probably be handled
in a server system by instructing the master thread to set new
values into its parameters, which *new session threads* would then
inherit from it, so that existing session threads keep the old values
On Tue, Aug 19, 2008 at 10:54 AM, Jörg F. Wittenberger
[EMAIL PROTECTED] wrote:
##sys#standard-{in,out}put are already handled specially (and
stored in the thread-state), so this doesn't make things any
more thread-safe than they already are.
a) I'm confused: I know that those ports are in
Jörg F. Wittenberger wrote:
are dynamic-wind pre/post-thunks by chicken executed upon each
thread switch?
Why would they?
In fact they don't:
(use srfi-18)
(thread-start!
(make-thread
(lambda ()
(dynamic-wind
On Tue, 19 Aug 2008, Jörg F. Wittenberger wrote:
Am Montag, den 18.08.2008, 09:19 -0700 schrieb Elf:
On Mon, 18 Aug 2008, Jörg F. Wittenberger wrote:
snip
as a sidenote, i cannot think of any legitimate reason to change timeouts
dynamically.
So you probably never had to debug a larger
On Tue, Aug 19, 2008 at 9:36 AM, Tobia Conforto [EMAIL PROTECTED] wrote:
Jörg F. Wittenberger wrote:
are dynamic-wind pre/post-thunks by chicken executed upon each thread
switch?
Why would they?
It's not a bad question. When threads are implemented using
continuations, it is reasonable to
Jörg F. Wittenberger scripsit:
To sum up: the approach feels not very clean to me. It would be much
more practical to add another argument to make-parameter and have it
support all three parameter designs, wouldn't it?
It's actually easy to get thread-global parameters without any
There are IMHO more important things we should concentrate on. There's
still
a) a broken SRFI-34 egg - something easily ignored
b) a race condition in the scheduler (which's fix I meanwhile fixed wrt.
to multiple threads waiting for the same fd, though I would not expect
that to ever happen;
On Tue, Aug 19, 2008 at 10:02 AM, Graham Fawcett
[EMAIL PROTECTED] wrote:
On Tue, Aug 19, 2008 at 9:36 AM, Tobia Conforto [EMAIL PROTECTED] wrote:
Jörg F. Wittenberger wrote:
are dynamic-wind pre/post-thunks by chicken executed upon each thread
switch?
Why would they?
It's not a bad
Hallo,
On Tue, Aug 19, 2008 at 11:52 AM, Jörg F. Wittenberger
[EMAIL PROTECTED] wrote:
There are IMHO more important things we should concentrate on. There's
still
a) a broken SRFI-34 egg - something easily ignored
b) a race condition in the scheduler (which's fix I meanwhile fixed wrt.
Am Dienstag, den 19.08.2008, 14:37 -0300 schrieb Alex Queiroz:
I don't know how many eggs you are currently using,
Frankly: I'm using just two (enviroments and libmagic) and because I'm
still sorta confused about dependencies, I copied both. The former
literally (my code was already
Hi Elf,
Am Dienstag, den 19.08.2008, 08:35 -0700 schrieb Elf:
On Tue, 19 Aug 2008, Jörg F. Wittenberger wrote:
There are IMHO more important things we should concentrate on. There's
still
where did this come from? did you cut off what you wre responding to?
Please safe both of us
17 matches
Mail list logo
