"R. Kent Dybvig" <dyb_at_cs.indiana.edu> writes:
>> Then the relevant section of our paper is directly applicable.
>
> Not at all. The mere existence of thread-local storage does not cause any
> problems. The problems arise with the hypothetical dynamic-binding and
> capture mechanisms described in the section. There's no reason to believe
> that they also arise with parameterize.
The section I was referring to (5.3) talks about thread-local storage,
and its negative effects. The problems aren't tied to any specific
dynamic-binding mechanism---as soon as you have thread-local cells,
(and you do) the problems arise. The paragraph that talks about
capture mechanisms (it doesn't talk about any hypothetical
"dynamic-binding mechanism, as far as I can see) identifies
*additional* problems, depending on the specific choices you make.
You may think that the choices you are the right ones, but they aren't
obvious, and come with a specific set of trade-offs. I personally
find remembering the particular choices made in a given system, and
their consequences for modular programs difficult, which is why I
dislike parameters.
--
Cheers =8-} Mike
Friede, V?lkerverst?ndigung und ?berhaupt blabla
Received on Fri Feb 23 2007 - 12:14:35 UTC