Describes how XPA access points can be added to X Toolkit (Xt) programs. ... Thus, in order to add XPA access points to the standard Xt event loop, the following routine should be called before entering the loop: int XPAXtAddInput(XtAppContext app, XPA xpa) . The XPAAddAddInput() routine will add XPA access points to the Xt event loop by making calls to the standard XtAppAddInput() routine. ... If the xpa argument is NULL, then all active XPA access points are added to the loop. ...

... Chapter 4: Solar System Targets > 4.2 Target Identification . ... The following information is required to identify and classify each target. ... For example, separate targets should be defined if you plan to take spectra of several different surface features on a planet, or if you plan to observe the same feature with different timing constraints. ... Description . PLANET . If the target is the center of a planet, enter PLANET followed by its name (e.g., PLANET JUPITER , PLANET SATURN ). ...

... The parameter pgdev allows the user to specify a pgplot device, but, in contrast to the pgplot standard, the file name should not be included, but instead supplied via the parameter plotfile . ... To write a colour postscript file called op.ps: pgdev=/cps plotfile=op.ps . However note that at present, if a colour postscript device ( pgdev = `/cps'), a fits file ( pgdev = `/fits') or a ppm file ( pgdev = `/ppm') are selected, the task in fact bypasses pgplot and writes the postscript file directly. ...

... Though Flint knows the interface definitions (i.e. number, type and intent of each argument) of standard FORTRAN functions, it is desirable for users to build and use a file (or files) describing the interfaces to their own library. ... The format is: flint -o file .. ... While these interface definitions could be input along with normal source files, preceding the interface file with the -l (library) switch has the advantage that the source of this file does not appear in the listing file. ...