Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!uflorida!bikini!thoth From: thoth@springs.cis.ufl.edu (Gilligan) Newsgroups: comp.windows.x Subject: Re: Toolkit re-entrant? Message-ID: Date: 8 Jul 90 16:25:05 GMT References: <4112@jato.Jpl.Nasa.Gov> Sender: news@uflorida.cis.ufl.EDU Organization: Cyborgs for Responsible CFC Use Lines: 29 In-reply-to: kaleb@mars.jpl.nasa.gov's message of 20 Jun 90 16:09:26 GMT In article <4112@jato.Jpl.Nasa.Gov> kaleb@mars.jpl.nasa.gov (Kaleb Keithley) writes: Are Xt and Xaw re-entrant? How about OpenLook or Motif? With more projects starting to use Ada, or SunOS 4.1 lightweight processes, or even shared libraries between processes is this likely to be a problem? Funny someone should mention lightweight processes. I've never gotten them to work under SunOS. Something about the non-blocking IO library interferes with the non-blocking IO used in the Xlib. I've tried to mangle the source so that it doesn't use O_NDELAY but I've only succeeded in causing it to print "Error: Can't open display" or some such babble. If anyone can hack the Xlib to use regular IO then I may be able to add threads to my applications. The non-preemptive nature of sunlwp should make it easy (for experienced programmers) to do multi- threading, but if we can paste monitors around the Xlib and Xt then we'll be much safer. I'd be much happier personally if xman could handle expose events and scroll requests while it was formatting. I end up forking and letting a subprocess write to a pipe which I XtAppAddInput to my application and handle piecemeil. Someone PLEASE patch Xlib. XtAppAddWorkProc is NOT a solution. Entirely too much state information. THOTH out -=O=- -- ( My name's not really Gilligan, It's Robert Forsman, without an `e' )