> Switching from philosophical to practical (not that being > philosophical is necessary a bad thing), is this a request to add new > typedefs?
Depends on how much size independence you want between the different pieces of code. I just know that things like DOMNodeList already return XMLSize_t and that was really the kind of thing that I was referring to. > E.g.: XMLCount_t, XMLLineCol_t, others...? > What about those APIs that currently return 'int' because they use -1 > to signal 'not found'? There's no requirement that the typedef be unsigned, but generally speaking I'm not found of that kind of idiom myself. XMLString::indexOf for example returns a position index, whereas I would have stuck with C idiom and returned the pointer or NULL for not found. People that care just do result - start if they need the position. But I don't know all the places where you're doing that, that's just one example I know of. -- Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
