Compilation warnings are not only ugly, they may indicate code that does not function as intended. I think it would be worth cleaning up the warnings. (I think it's a good idea to leave the inlining warnings alone, since that's highly compiler-dependent.)
Unfortunately, I'm way down-level, so I can't help. Maybe you could clean up the code that you can adequately test? -----Original Message----- From: Don Mastrovito [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 11:48 AM To: [EMAIL PROTECTED] Subject: Compilation warnings When I first became involved with Xerces, I was amazed at the number of compilation warnings generated when rebuilding the library. I had always assumed that because Xerces was a work-in-progress, that these would eventually be cleaned up. That doesn't seem to be the case. I could make the edits but don't have the ability to adequately test *all* the changes. Most are nearly all trivial edits. Alternately, I (and hopefully others) could fix things one module at a time. Is there interest in addressing the warnings? I don't see suppressing them as a permanent solution. It merely hides potentially bad code or bad coding practices. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
