Re: [xml] xmlSplitQName2 problem and patch

But why does this function return NULL in this case?
Shouldn't it return the passed in string (in the same
way as xmlBuildQName() function does)? The current 
code returns NULL in error case too and this makes
a confusion (IMHO).


Daniel Veillard wrote on 2/18/2004, 1:28 AM:

  No, it's really on purpose. The goal is to minimize string allocations, 
if the argument passed is an NCName, then no new string will be allocated. 
The client code might be slightly more complex as a result but string 
allocations and freeing is really very costly, so I try to avoid it as 
much as possible, that's why I designed the function that way. 

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]