Abdulaziz Ghuloum <aghuloum at cs.indiana.edu> writes:
> On May 24, 2007, at 3:19 AM, Michael Sperber wrote:
>
>>
>> Abdulaziz Ghuloum <aghuloum at cs.indiana.edu> writes:
>>
>>> Section "8.2.6 Input and output ports" says that the
>>> procedure transcoded-port closes the binary port before
>>> returning the new textual port. Is there any way to
>>> undo this side effect so that we get the original
>>> binary port functional again?
>>
>> No.
>
> May I ask why not?
I believe the issue is that there would be shared state between the
original binary port and the new textual port, and state changes on one
might not make sense for the other. (5.91 had a different model, but
the subsequent discussion resulted in the changes in this area.) Thus,
the notion of "original binary port functional" doesn't always make
sense.
--
Cheers =8-} Mike
Friede, V?lkerverst?ndigung und ?berhaupt blabla
Received on Fri May 25 2007 - 09:21:16 UTC