To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=82995
------- Additional comments from [EMAIL PROTECTED] Tue Oct 30 17:04:31 +0000 2007 ------- My opinion is the following: Ultimately, all OOo code should be coded in an exception-aware way and be compiled with exceptions enabled, and plain new should always be standards conforming (i.e., throwing bad_alloc, not returning NULL). The code should move toward that goal, not away from it (and it should ideally do so in a way that interim versions of the code do not start to hide or obscure bugs that would have been well visible in prior versions). This implies two things: 1 When calling new can "legitimately" fail (e.g., because the requested size can be enormous as it is a value coming from the outside, not a programming error or the---unlikely---case of "real" memory outage), fix the code (e.g., by compiling with exceptions enabled and handling bad_alloc, or by using new(nothrow)). This apparently happened for issue 82970. 2 Improve the Windows build environment to make plain new throw bad_alloc (or abort) when compiling with -fno-exceptions -DEXCEPTIONS_OFF (if possible). --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
