http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1427 *** shadow/1427 Fri Apr 20 04:33:16 2001 --- shadow/1427.tmp.6823 Fri Apr 20 04:33:16 2001 *************** *** 0 **** --- 1,33 ---- + +============================================================================+ + | AttributeList.getValue() returns odd value for empty string | + +----------------------------------------------------------------------------+ + | Bug #: 1427 Product: Xerces-C | + | Status: NEW Version: 1.4 | + | Resolution: Platform: HP | + | Severity: Normal OS/Version: HP-UX | + | Priority: Component: DOM | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + The documentation for AttributeList.getValue(const char*name) states that + if the attribute doesn't exist, null is returned. + + This *is* in fact the case if the attribute doesn't exist at all, but if it is + defined to be an empty string, then something *other* than null is returned. + In addition, this value (I haven't checked exactly what it is) causes + XMLString::transcode to return a null pointer. + + example: + <sometag item=""/> + getValue("nosuchattribute") returns null + getValue("item") returns non-null. + + I suggest that an attribute which has a value of empty string should cause + getValue() to return null. If there is a reason not to do this, then could we + please at least have some documentation update about the getValue(name) method + to describe this empty-string behavior? Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
