Opened 17 years ago
Closed 17 years ago
#164 closed defect (fixed)
QName docs. are bad, need to clarify acceptable input
Reported by: | TerryBrown | Owned by: | cmlenz |
---|---|---|---|
Priority: | major | Milestone: | 0.5 |
Component: | General | Version: | 0.4.4 |
Keywords: | Cc: |
Description
The docs. describe a QName as '{foo}bar'. The examples show the unexplained and unintuitive 'foo}bar' form. Constructing from '{foo}bar' gives a QName that prints as 'foo}bar', but with an underlying string of '{{foo}bar'. QNames constructed with the leading '{' fail to work as expected in stream filters, drop the leading '{' and everything works fine.
Either the docs. need to shout that the leading '{' can't be used, or the class needs to handle it better.
Change History (2)
comment:1 Changed 17 years ago by TerryBrown
- Summary changed from QName docs. are bad, need to clarify acceptable inputoob to QName docs. are bad, need to clarify acceptable input
comment:2 Changed 17 years ago by cmlenz
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Fixed in [782].