[Ecls-list] gray-stream support

[Stelian Ionescu]

On Wed, May 07, 2008 at 02:10:03PM +0200, Juan Jose Garcia-Ripoll wrote:
>On Wed, May 7, 2008 at 1:22 PM, Stelian Ionescu
> <sionescu at common-lisp.net> wrote:
> > On Tue, May 06, 2008 at 02:24:24PM +0200, Juan Jose Garcia-Ripoll wrote:
>>  >But this is a problem with trival-gray-streams, isn't it? I mean it is
> >  >exporting its own symbol stream-read-sequence. But why would they do
> >  >that if the Gray package already provides it?
> >
> >  because not all implementations define stream-read-sequence, so T-G-S
> >  defines its own stream-read-sequence, which calls whatever the
> >  implementation supports
>
> There is a more subtle issue, which is that not all implementations
> define stream-read-sequence with the same kind of arguments. Lispworks
> seems to have (stream seq start end), while SBCL and ECL use (stream
> seq &optional (start 0) end), etc, etc.

that too, but I was referring to OpenMCL having
stream-{read,write}-vector instead, and CLISP having
stream-{read,write}-{byte,char}-sequence instead of stream-{read,write}-sequence

> I did not think about it, but
> it is probably because the original "specification" did not contain
> stream-read/write-sequence.

yes, probably

-- 
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20080507/03bd880e/attachment.sig>