Re: [Openexr-devel] A few fixes before the 1.1.0 release

[Drew Hess]

Hi Brad,

Yeah, that fix didn't make it into last night's CVS update.  I will tackle 
it before the 1.1.0 release.

Florian tells me that for the SGI compiler, "restrict" made a big 
difference in Imath, but nobody has really tested whether it makes any 
difference with gcc, Intel icc, or Microsoft VC++, so I'm tempted just to 
remove it unless someone has time to demonstrate that it's useful.  It's a 
fairly nasty portability issue since we need to make OpenEXR work with at 
least 4 different compilers, all of which seem to handle restrict slightly 
differently (even though it's officially part of C99).

Anyway, I'll spend some more time looking at this in the next few days 
when I have a chance, and see what we can do about it.


-dwh-


On Sat, 31 Jan 2004, Brad Hards wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sat, 31 Jan 2004 00:16 am, Drew Hess wrote:
> > Hi all,
> >
> > I just checked in some changes that needed to be made before a 1.1.0
> > release.  Among them are:
> Drew,
> 
> I'm looking forward to seeing 1.1.0 - thanks for the work on this.
> 
> Only one question - have you though about the restricted pointer issue any 
> more? There are a couple of options, and it perhaps isn't especially 
> critical, but I'd like a solution at some stage.
> 
> Brad
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> 
> iD8DBQFAGuMWGwwszQ/PZzgRAkmWAJsE8WtSo9us15LuuPmuk/Z1S7rWrQCgl+/e
> jqzvc9/4unHjGww2vdxFzWs=
> =cycx
> -----END PGP SIGNATURE-----
> 
> 
>