> > MIPSpro does not honor the C++ thing where variable scope is kept withing a > for loop (for example) and so in the instance where the same variable name > was > used twice in the same function within seperate scope, i had to change one to > be different so that MIPSpro could cope. > > would i be asking too terribly much to ask that the the variable scope rules > meet that of plain old C so that blackbox will cleanly build on SGI kit using > MIPSpro as the compiler? > > there were only, i think maybe 4 or 5 instances of this happening, so it's > not > a terribly huge undertaking, and would help out tremendously thouse of us who > like to use MIPSpro. >
that is so amazingly lame. lame. lame. I will accept a patch (diff -pru) for this. However I can not promise we will not forget to follow this in the future. You should contact the compiler vendor and inform them the year is 2002 a.d./ c.e./whichever and there is an ISO C++ standard they should be following.
