🚀 go-pugleaf

 
> Woe is you....  I presume that you built your application with the FORTRAN
> API to PHIGS.  If so, you can eliminate the hope of using any PEX related
> libraries (PEXlib, PHIGS API to PEX) and you can probably eliminate the
> use of IBM's graPHIGS API (though you may be able to use the PHIGS API
> to graPHIGS - I don't know for sure.)
> 

graPHIGS has an ISO Fortran binding which your application is wriiten in.

> I do know, however, that you can use our product, FIGARO+, because we
> conform to the ANSI/ISO PHIGS standard for both FORTRAN and C.  You will
> definately have to do some editing because there are differences in
> implementation between DEC PHIGS and FIGARO+, though they're usually not
> differences in function names/parameters, but rather differences in 
> interpretation of the standard.  Our customers have been sucessful in 
> transitioning from DEC PHIGS to FIGARO+.
> 
> The major benefit of doing so is that when you're ready to work on an
> SGI or SUN or CRAY or PC or whatever (in addition to DEC VAX, Ultrix, and
> IBM RS/6000, CMS, and MVS), you just recompile and relink!
> 

Definitely a plus if you are looking for across platform portability.
I have little experience with FIGARO+, but I assume it is written on top of
GL or graPHIGS, so performance can be an issue, depending on the application.


Greg


____________________________________________________________
Gregory J. Scallan                       |  IBMnet:     GSCALLAN@KGNVMY
Graphics Systems Technical Center, AWSD  |  Internet:   spider@vnet.ibm.com
(914)385-5054  (T/L 695)                 |  Sneakernet: 203-2-2-2, Kingston