Why libxml2 uses "BAD_CAST" everywhere in a C/C++ code?

Viewed 2275

It's said that because libxml2 uses unsigned char as storage to make encoding/decoding between char sets convenient ---- isn't it ugly to force users to write "BAD_CAST" everywhere in the code, when reading/creating xml node names, contents, text nodes, etc.

It there a way to avoid writing such "BAD_CAST" everywhere? The design is really so bad.

1 Answers
Related