I see that are both LCP and non-LCP are implemented using the same TEC structures (transcoders), but I meant more in an object hierarchy sense -- since the core implementation is similar, why not build one transcoder that fulfills both LCP and non-LCP interfaces?
I was hoping to create a non-LCP transcoder, but be able to use UINT calcRequiredSize(char*) or XMLCh* transcode(char*). Right now I'm using a dog stupid method of allocation; four times as many characters as the input string. Adam Heinz Senior Software Developer Exstream Software --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
