Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!samsung!eileen!gjc
From: gjc@mga.COM (George J. Carrette)
Newsgroups: comp.windows.x
Subject: Re: XtAddInput problem
Message-ID: <112@eileen.mga.com>
Date: 11 Nov 89 14:06:28 GMT
References: <8911081827.AA12003@turnpike.sun.com> <294@nap1.cds.wpafb.af.mil>
Organization: MGA, Inc.
Lines: 12
In-reply-to: staatsvr@asdcds.cds.wpafb.af.mil's message of 9 Nov 89 17:29:19 GMT

XtAddInput works great in VMS, exactly as one would expect, with no
funny glitches. The only problem is that it limits you directly to a
QIO level interface, (or an AST EVENT/FLAG one if you are clever).
Getting access to the usual record-management-services level is a bit
tricky. But being able to use the VAX-C run-time-library with its
fopen/open and getc/puts read/write is hopeless (undocumented
internals structure). 

So the portability aspects of the thing are hopeless, unless you punt
the DIGITAL provided C-runtime-library for your own. 

-gjc