[ http://issues.apache.org/jira/browse/XALANC-493?page=comments#action_63596 ] Dmitry Hayes commented on XALANC-493: -------------------------------------
I agree, it's a good idea to make the assert more common. Probably we should open the macro for the release build too: I'd assume that the user first builds the release version of the library, and only in case of problems, starts the debugging process. It's very probably that all the modern compilers remove unused temporary objects, so the assert wouldn't affect the performance in the release mode. > Problem with XALAN_STATIC_CHECK on HP-UX IA64 > --------------------------------------------- > > Key: XALANC-493 > URL: http://issues.apache.org/jira/browse/XALANC-493 > Project: XalanC > Type: Bug > Components: XalanC > Versions: CurrentCVS > Reporter: David Bertoni > Assignee: David Bertoni > Attachments: patch.txt > > There is a problem with the definition of the underlying class on this HP > platform. Plus, I believe we can expand the use of this macro, so we should > move it to a more general location. > This patch moves the definition of this macro to PlatformDefinitions.hpp for > the time being. If the number of compile-time asserts we use grows, we can > move these to a separate file. Also, I've written it in such a way that it > compiles out on release builds, although I'm not sure if that's the right > thing to do. > Committers, can you please review the patch? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
