🚀 go-pugleaf

In article <63918@hydra.gatech.EDU> gt8166a@prism.gatech.EDU (DOERSCHUK,DAVID OAKES) writes:

>I am taking a graphical interfaces class, and the system being
>used is PHIGS on Sun ipc machines.  I'm having a difficult time
>of it, in part because the text ("A Practical Introduction to
>PHIGS and PHIGS PLUS", by T.L.J. Howard, et.al. c.1991) does not
>seem to use the same names for functions, structures, and #defines
>as Sun PHIGS does.  I'm told that our version of Sun PHIGS is the
>most recent, although I can't find the version number by grepping
>the .h files for "ersion" and "ev" ({V|v}ersion and {R|r}ev). 

You are using SunPHIGS 2.0 (or later, possibly). This was the first version
to use the recently released ISO C binding to PHIGS. Previously, there was
no standard binding to use PHIGS from C, so each vendor made up their own.

The Howard et al book was published in 1991, before the ISO C binding was
published. Therefore, although it uses SunPHIGS, it uses the previous
binding. The actual concepts in the book are still valid. In many cases the
function names have simply changed by having underscores added.

There is a script supplied with SunPHIGS2.0 to convert the old SunPHIGS C
binding to ISO C. You could run that over any examples that use the old
bindings. 

There are man pages for the phigs functions. So, for example, you can type:

man popen_phigs

and get a page of description. You will need to make sure your manpath is
appropriately set up, depending on where your system administrator has put
the PHIGS man pages.

>Dave Doerschuk
>Georgia Institute of Technology, Atlanta Georgia, 30332
>uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt8166a
>Internet: gt8166a@prism.gatech.edu

Chris Lilley			lilley@cgu.mcc.ac.uk
Computer Graphics Unit, University of Manchester, UK