From: Michel.Mauny@inria.fr (Michel Mauny)
To: Choun-tong.Lieu@litp.ibp.fr (Choun-Tong LIEU)
Cc: caml-list@pauillac.inria.fr
Subject: Re: stream
Date: Wed, 28 Feb 1996 19:36:42 +0100 (MET) [thread overview]
Message-ID: <199602281836.TAA07199@pauillac.inria.fr> (raw)
In-Reply-To: <199602280938.KAA02520@cadillac.ibp.fr> from "Choun-Tong LIEU" at Feb 28, 96 10:38:10 am
Bonjour,
> J'ai une conversation "bizarre" avec caml-light a propos des
> stream. J'ai essaye de fouiller dans les docs, je n'ai pas trouve de
> reponse.
>
> Est ce que caml-light privilegie le dernier element non
> terminal des stream ?
> [...]
> #pr toto;;
> 123- : unit = ()
(***** Je comprends un peu moins ou pas du tout. Remarquons tata est a la fin
> de [< toto; tata >]
> *****)
C'est un comportement décrit dans la liste des bugs connus de
Caml-Light 0.7. Vous vous attendiez à juste titre à ce que "tata"
soit vidé par le parcours de [< toto; tata >].
Vous trouverez ci-dessous un extrait du fichier KNOWN-BUGS de la
distribution 0.7, qui indique notamment comment contourner ce bug.
Cordialement,
--
Michel Mauny
---------------------------------------------------------------------------
The following problems have not been fixed at the time of this release:
1- Stream concatenation using [< ... >] does not always preserve the
sharing among streams, and sometimes duplicate stream subcomponents.
For instance, if you define s' = [< '1; s >] and then read alternatively
from s' and from s, a given element of s can be read twice.
The problem occurs only if s is in tail position inside s'.
To guarantee proper sharing, move s in non-tail position, e.g.
take s' = [< '1; s; [<>] >].
---------------------------------------------------------------------------
prev parent reply other threads:[~1996-02-29 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-28 9:38 stream Choun-Tong LIEU
1996-02-28 18:36 ` Michel Mauny [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199602281836.TAA07199@pauillac.inria.fr \
--to=michel.mauny@inria.fr \
--cc=Choun-tong.Lieu@litp.ibp.fr \
--cc=caml-list@pauillac.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox