all groups > dotnet xml > march 2005 >
You're in the

dotnet xml

group:

Should System.Xml.NameTable be deprecated?


Should System.Xml.NameTable be deprecated? Mark Bosley
3/21/2005 12:21:54 PM
dotnet xml: There seems to be little interest in this object, the docs are wrong and it
doesn't do much.

Two years ago, it was pointed out that the documentation is nonsensical
(http://groups-beta.google.com/group/microsoft.public.dotnet.framework/browse_thread/thread/3e621115f78943e2/38232c4e9c0bdd64?q=Marcus+NameTable#38232c4e9c0bdd64)
, the documentation remains unchanged.

The one example that makes any sense at all is found at
http://www.csharpfriends.com/articles/getArticle.aspx?articleID=309&page=2

But even reading a 52MB file, it provides about a 10% boost.
So, MS, please .. correct the documentation or be rid of it.

Sincerely, Mark B.

Re: Should System.Xml.NameTable be deprecated? Oleg Tkachenko [MVP]
3/22/2005 1:48:05 PM
[quoted text, click to view]

NameTable is too important to be got rid.

--
Oleg Tkachenko [XML MVP, MCP]
Re: Should System.Xml.NameTable be deprecated? Helena Kupkova
3/22/2005 7:04:28 PM
Hello Mark,

NameTable is a very useful thing to have in XmlTextReader. It makes sure
that each name is allocated only once and that name comparison that is so
often in XML processing can be done efficiently by just comparing string
references instead of doing the full string comparison. Just think how many
string comparisons must be done to implement duplicate attribute checking or
namespace lookups. If we were to allocate a string for each name in the
document, the parser would be waaayyy slower.

Thanks,
Helena Kupkova, Microsoft


[quoted text, click to view]

AddThis Social Bookmark Button