Re: Porting to 2.0

New Message Reply Date view Thread view Subject view Author view

Dave Russell (drussell++at++vsl.ist.ucf.edu)
Fri, 22 Mar 1996 08:02:59 -0500

Gary Williams wrote:
>
> > My advice is to go back to the customer and explain that porting
> > to 2.0 is really not that difficult, and that all registered 1.2
> > users with software maintenance get a free copy, etc., and see if
> > there is some way to make the transition happen. ...
>
> OK... Since you addressed porting to 2.0, I've got a couple questions.
>
> First, I've been monitoring the Performer mail list for a couple months or so
> and it seems numerous bugs have been reported with 2.0. I haven't researched
> the 1.2 bug list, but which is more stable (more to the point, how risky is the
> port)?
>
This I can't answer; hopefully, some of the SGI guys can give some of
their opinions. In most cases, the bugs that have been reported tend to
be with the new features which you probably won't be using at first
anyway. Still, I'm no authority.

> Secondly, our apps are written in C++, not C. I saw a message the other day
> that the porting scripts don't handle C++ apps. Is this correct or did I
> misunderstand something? If I did read it correctly, any suggestions on
> efficiently porting C++ apps?
>
I'm not sure about the porting scripts handling C++. I imagine that the
problem is not in your code being C++, but rather porting to the C++
API. Just because you have your code written in C++ doesn't mean you
need to use the Performer C++ API. Right now you are making standard C
calls to the Performer 1.2 API, so the port to 2.0 should be relatively
painless. None of our ports have taken more than a day or two (no one
here has even used the porting scripts), and as far as I know, we don't
have any bugs created by 2.0.

I ported all of my code to the C++ API in a day. That, of course, was a
quick and dirty port just to get everything working in the new
environment. Since then, I've spent about three weeks completely
rewriting the structure of my code to utilize some of the new features
of 2.0. Of course, my code is a database handler that I've rewritten to
use pfBuffer's so that created a serious overhaul. Your mileage will
definitely vary.

For anyone that's interested, my pfBuffer bugs have disappeared along
the way. Not sure why, but everything seems to be working very well.

<.....STUFF CUT.....>

>
> Gary
>
> ******************************************************
> GARY E. WILLIAMS, Capt, USAF
> Air Force Institute of Technology
> MS Student in Computer Systems: Modeling & Simulation
> Official Email: gewillia++at++afit.af.mil
> Personal Email: Sleuth61++at++msn.com
> http://www.afit.af.mil/ENGgraphics/people/gewillia/index.html

-- 
David Russell				|    	
Visual Systems Lab			|	Static worlds breed	
Institute for Simulation and Training	|	   static minds.
					|	     
drussell++at++vsl.ist.ucf.edu		|   CHANGE YOUR (virtual) WORLD!

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:52:34 PDT

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