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 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 the thread state, but
I'm confused about interaction of call/cc and threads: are
dynamic-wind's all executed upon each thread switch or not at all?
This is especially interesting wrt. to parameters too.
b) I noticed meanwhile that this "fix" did at least not fix the problem
I have: output from elsewhere appearing in the file I opened by
with-output-to-file - probably because the output came from
##sys#schedule/switch
c) my patch uses in with-*-*-file the same code structure as for
instance unit ports with-*-*-string. Why should one do it this way and
one the other way?
> Additionally, it may not always be intended to close the port
> when an escaping continuation is used, as the current state
> could be re-entered.
I understand your remark, but I don't understand it's relationship to
the code in question. IMHO the escaping continuation should not close
the port.
/Jörg
_______________________________________________
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
