Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!bloom-beacon!deccrl!news.crl.dec.com!decvax.DEC.COM!evans
From: evans@decvax.DEC.COM (Marc Evans)
Newsgroups: comp.windows.x
Subject: Re: XtAddInput question
Message-ID: <519@decvax.decvax.dec.com.UUCP>
Date: 24 Jan 91 19:29:25 GMT
References: <1991Jan18.200129.21797@linus.mitre.org> <980@attc.UUCP>
Sender: news@decvax.dec.com.UUCP
Reply-To: evans@decvax.DEC.COM
Distribution: na
Organization: Synergytics
Lines: 28

In article <980@attc.UUCP>, marbru@attc.UUCP (Martin Brunecky) writes:
|> In article <1991Jan18.200129.21797@linus.mitre.org> daf@cavern.mitre.org (Dennis A. Franciskovich) writes:
|> >when the file *can* be read, not just when there is new input to read.
|> 
|>    Can someone explain to me what are the semantics and mechanisms of a file
|>    (not a pipe or a socket) that *can* be read but there is NO *new input* 
|>    to read ?????

From what I have been able to gather, people really should be doing a

    #ifdef unix
	XtInputId InId;
	CARD32 mask = XtInputReadMask | XtInputExceptMask;
	FILE *fp = popen("tail -f {filename}","r");
	
	if (fp)
	{ InId = XtAppAddInput(appC,fileno(fp),mask,myfunc,NULL); }
    #endif

In other words, they seem to think that the XtAppAddInput and XtAddInput
functions should be performing the task performed by the u*x tail command.

- Marc
-- 
===========================================================================
Marc Evans - WB1GRH - evans@decvax.DEC.COM  | Synergytics     (603)635-8876
      Unix and X Software Contractor        | 21 Hinds Ln, Pelham, NH 03076
===========================================================================