Re: Class Libs for Performer

New Message Reply Date view Thread view Subject view Author view

Jim Helman (jimh++at++surreal)
Thu, 23 Feb 95 18:17:20 -0800

> For us that have encapsulated the C binding into an C++ application
> framework with supporting classes, we will have to see what advantages
> there will be to SGI's new binding. If SGI is willing to let us take a
> sneek peek at the C++ design we could be preparing our toolkits for
> the release. How about it, SGI?

The API part is easy, since 90% or more of the C++
API is just what you'd expect. Performer's API is
sufficiently regular that most of the CAPI is now
automatically generated from the C++ API.

The basic rules for translating a Performer C
binding into the corresponding C++ binding are to
add the "set" that is implicit in the C API, and to
drop the class name present in the C API.

         CAPI C++

pfMtlColor(mtl, token, color) mtl->setColor(token, color)
pfGetMtlColor(mtl, token) mtl->getColor(token)
pfApplyMtl(mtl) mtl->apply()

As for other design issues, we're adding some new things
for type extensibility and such, but for performance
reasons, we're staying away from any radical redesign of
our traversal methodology.

rgds,

-jim helman

jimh++at++surreal.asd.sgi.com
415/390-1151

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:51:00 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.