I've been trying to figure out how to activate the gnu_compat flag that ube apparently supports via cc -Wu,<option here>.
I suspect that this should fix the problems I'm having compiling code that uses a few common gcc extensions such as range of values initialisation syntax for arrays like: array[ 0 ... 0x80 ] = value; *rant follows, read only if you work for Sun* Which brings me to a side question of *why the bleepity bleep* would you ship functionality and then not document it at all? It isn't very fair to folks that use Sun Studio to be tormented and teased with compiler options that would solve our immediate problems while internal Sun folks are freely available to use them. Yes they may break into pieces and I get to keep all of them, but that's what interface stability documentation is for. These options should be at least listed somewhere under "NOT SUPPORTED IN ANY WAY complaints go to /dev/null" or stability volatile. Whatever assuages your conscience. Withholding valuable functionality that obviously works well enough to let internal Sun folks use and shipping it to external users without letting them know how to use it is rather infuriating. Thanks, -- Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth _______________________________________________ tools-discuss mailing list [email protected]
