---- I just ate about 7 pounds of meat -theantix
You fix the errors, change the code to eliminate three of the warnings and decide to live with the other two. Now you have: no errors, two warnings.
This sucks; once you have attended to things you should get a clean compile. There should be declarations that you can wrap around dodgy code, muffling specific warnings and documenting why you don't care. So you start with: three errors, five warnings, no notes. You end up with: no errors, no warnings, two notes.
From time to time you should look in notes.log to see what the notes were about and review the reasons you gave for not pursuing the matter. Current practise implicitly schedules such a review for every compile, which is obviously too often.
Bill Shannon, along with Bill Joy and Rob Gingell, was one of the founding Unix gods of Sun's OS. I don't know if that code was brought over (1994 or so) when Solaris sprang from head or rib of SunOs.
I don't know if it ever got displayed, but I know that a lot of Sun hot shots spent a lot of their free time trying to make it come up.
That's not a stupid compiler message, but it is a Sun error message story so I hope it's not inappropriate here.Buy my books, dammit!
