jez 9b32ed13e4 Some time ago, it was gently suggested to me that XPathValuePtr and XPathExpressionPtr both exposed an implementation detail, because they derive fromboost::shared_ptr, and provided an interface that was inconsisted with the DOM classes, because you accessed the member functions via -> rather than . ... At the time, I was just pleased to have got the XPath stuff done and wasn't really fussed, so I left it. Since then though, it's niggled and niggled away at the back of my mind and now I've decided to do something about it. XPathValuePtr will become XPathValue, with the member functions accessed through the . operator. The XPathValuePtr name and -> member access will be retained for the meantime, so that existing code won't be broken. XPathExpressionPtr will be similarly changed. This commit is the first bit of that work, now I've satisfied myself it's going to be pretty easy so long as I pay proper attention.		2007-10-19 21:59:24 +00:00
..
CppUnit	reworked test builds to use Automakes built in check target	2007-08-29 02:03:12 +00:00
DOM	sorted out makefiles to fix dist targets	2007-09-11 09:25:18 +00:00
SAX	renamed include/Utils to include/Arabica	2007-09-10 17:52:04 +00:00
silly_string	renamed include/Utils to include/Arabica	2007-09-10 17:52:04 +00:00
Utils	more namespace and file moving shenanigans	2007-09-10 17:24:17 +00:00
XPath	Some time ago, it was gently suggested to me that XPathValuePtr and XPathExpressionPtr both exposed an implementation detail, because they derive fromboost::shared_ptr, and provided an interface that was inconsisted with the DOM classes, because you accessed the member functions via -> rather than .	2007-10-19 21:59:24 +00:00
XSLT	moved DOM streaming from Utils/ to io/	2007-09-13 21:21:55 +00:00
Makefile.am	reworked test builds to use Automakes built in check target	2007-08-29 02:03:12 +00:00