http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1303 *** shadow/1303 Wed Apr 11 01:21:33 2001 --- shadow/1303.tmp.16723 Wed Apr 11 17:13:57 2001 *************** *** 2,11 **** | AttrImpl::setValue with null argument | +----------------------------------------------------------------------------+ | Bug #: 1303 Product: Xerces-C | ! | Status: NEW Version: 1.4 | ! | Resolution: Platform: All | | Severity: Normal OS/Version: All | ! | Priority: Component: DOM | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | --- 2,11 ---- | AttrImpl::setValue with null argument | +----------------------------------------------------------------------------+ | Bug #: 1303 Product: Xerces-C | ! | Status: RESOLVED Version: 1.4 | ! | Resolution: FIXED Platform: All | | Severity: Normal OS/Version: All | ! | Priority: High Component: DOM | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | *************** *** 34,37 **** this happend to me on DYNIX/ptx numa 4.0 V4.4.7 i386 with gcc 2.95.3 and Linux with gcc 2.95.2 ! but I think it doesn't matter --- 34,44 ---- this happend to me on DYNIX/ptx numa 4.0 V4.4.7 i386 with gcc 2.95.3 and Linux with gcc 2.95.2 ! but I think it doesn't matter ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-04-11 17:13 ------- ! Setting the value to null is risky to say the least. I wouldn't be surprised ! someone chokes on it down the line. On the other hand I agree that behaving as ! a no-op for that matter doesn't seem right. So I changed the code to simply ! accept the null value. I leave it to the caller to take responsability for the ! possible consequences... :-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
