caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Francois Rouaix <francois@rouaix.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Labltk.Fileevent for both r and w
Date: Mon, 17 Mar 2003 16:59:52 +0100	[thread overview]
Message-ID: <7D31FE8F-5891-11D7-8289-000A95773ED2@rouaix.org> (raw)
In-Reply-To: <20030314003713.E748@max.home>

Hi,

I vaguely remember that the problem was a defiency of the early 
versions of Tk (you know, back in the 4.x versions). Of course, it 
would now make sense to have a better interface to the Tcl FileHandler 
API.
We could have a camltk_createfilehandler and camltk_deletefilehandler 
mirroring the Tcl API, allowing for the TCL_READABLE and TCL_WRITEABLE 
flags, with backward compatibility for the old API implemented with the 
new one (e.g. add_file_input would call createhandler with 
TCL_READABLE).
Seems possible.
Anyone has the time to write a patch ;-) ?

--f
François Rouaix


> 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

-------------------
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-17 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13 18:37 Max Kirillov
2003-03-17 15:59 ` Francois Rouaix [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=7D31FE8F-5891-11D7-8289-000A95773ED2@rouaix.org \
    --to=francois@rouaix.org \
    --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).