caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Max Kirillov <max630@mail.ru>
To: caml-list@inria.fr
Subject: [Caml-list] Labltk.Fileevent for both r and w
Date: Fri, 14 Mar 2003 00:37:13 +0600	[thread overview]
Message-ID: <20030314003713.E748@max.home> (raw)

Hello!

I've noted that I cannot set both Fileevent.add_fileinput and
Fileevent.add_fileoutput. A short course to sources showed that is seems
to be true: when you call

Tcl_CreateFileHandler(tcl_filehandle(fd), TCL_READABLE, 
                       FileProc, (ClientData)(Long_val(cbid)));

from the otherlibs/labltk/support/cltkFile.c (camltk_add_file_input),
it removes the handler for writing, according to



       There  may  exist  only one handler for a given file at a given time.
       If Tcl_CreateFileHandler is called when a handler already exists	 for
       fd,  then  the  new callback replaces the information that was previ╜
       ously recorded.

(from Tcl_CreateFileHandler(3))

And vice versa.

This is not very useful on ordinary files and pipes,
but it is on sockets and some devices.

This may be worked around using dup, but it is greatly unconvenient.
Is there an option to enable the coexistence of the handlers? I see it
making one function camltk_{add/remove}_file_io, which
installes some wrapper for the case of two handlers, and then the
wrapper chooses the right handler accordind to the mode. This may be
done either in C code (in function FileProc in the same file) or in
ocaml.

-- 
Max

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


             reply	other threads:[~2003-03-13 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13 18:37 Max Kirillov [this message]
2003-03-17 15:59 ` Francois Rouaix

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=20030314003713.E748@max.home \
    --to=max630@mail.ru \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).