[osg-submissions] std:: namespace include for rand inSoftShadowMap.cpp

[Robert Osfield]

On 8/16/07, Jean-Sébastien Guay <jean-sebastien.guay at polymtl.ca> wrote:
> I would assume so. That's what I had done about 6 years ago when I was
> working on a renderfarm management software that ran on IRIX. Moving
> to gcc involved some work to get it to compile the first time (about 2
> weeks IIRC) but after that it went smoothly. For OSG since it already
> compiles with g++ on other platforms I assume compiling it with g++ on
> IRIX would be pretty painless, depending on the version of g++ that's
> available on IRIX...

Oh the OSG probably already compiles just fine with g++ on IRIX, its
end user applications that will be the limit on dropping MipsPro
support.

> But I would assume performance would suffer a bit as g++ will probably
> optimize a bit less than IRIX's own compiler. At least, that was the
> case for the project I worked on, but it didn't make enough of a
> difference to be significant. For an OSG project it might be more
> important, but that's up to the actual user to test out, compare and
> determine if it makes a difference for them.

Performance under IRIX really not something we need to worry about -
its really just an issue of supporting apps that have to run on this
legacy hardware/OS.

> > For 2.2 I'm not about to entertain dropping IRIX or VS6.0 support as
> > we're so close to the release, and those lagacy users need a stable
> > base to work from if future versions won't be available.
>
> That's good, especially if it works well as-is. I was not suggesting
> dropping support for anything, just giving my impressions on the usage
> experience.

Feedback appreciated.  I find it rather amazing how problems that were
plagued us back in late nineties still dog us today, almost a decade
of problems with VS and MipsPro...  It all down to legacy harward and
software systems being kept around forever, long after their sell by
date...

Robert.