New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
close_in twice does not raise an exception #3426
Comments
Comment author: administrator
This point has been hotly debated among the Caml team, and I'm not (Caml folks: what is the consensus? Should we fix the implementation
|
Comment author: administrator Date: Mon, 15 Jul 2002 10:04:02 +0200 (MET DST)
(Caml folks: what is the consensus? Should we fix the Pour close, traditionnellement, on peut le faire aussi. Par contre, Bref, c'est plutôt un problème de compatibilité ascendante, il me Bruno. |
Comment author: administrator Quelques informations supplémentaires, après relectures à droite et Date: Wed, 17 Jul 2002 14:48:27 +0200 (MET DST) Pour close, traditionnellement, on peut le faire aussi. Par Bref, c'est plutôt un problème de compatibilité ascendante, il me Maintenant que flush ne fait plus d'erreur, aucun des 2 close ne Dernière note: si on fait plus strict, sur EBADF [il y a aussi EINTR CAMLprim value caml_close_channel(value vchannel) ceci car le close peut avoir été fait sur le fd directement Bruno. |
Comment author: administrator Updated documentation to match implementation. XL, 2002-07-18 |
Comment author: administrator
Bon, j'ai corrigé le manuel pour documenter le comportement "laxiste"
|
Original bug ID: 1235
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Emmanuel Renieris
Version: 3.02-3.04+15
OS: Linux/Solaris
Submission from: miette.cs.brown.edu (128.148.38.66)
Typing in the following at the top level does not raise an exception. the manual
says it should.
let c= open_in "/dev/zero" in close_in c; close_in c;;
This is true on a Linux debian testing 2.2.20, and on Solaris 7.
Our Ocaml is 3.02 on Solaris and 3.04 and 3.04_15 on the Linux boxes.
Of course, there's probably code out there that depends on it...
The text was updated successfully, but these errors were encountered: