> Well, I would argue that for (what I would guess are) most xerces use > cases, the CF transcoder works just fine.
But they don't for mine, and I'm the one stuck dealing with that, so I'm just voicing my opinion. As I said, I'm basically "voting" and if there's no vote or others disagree, so be it. For me, it causes a lot of trouble, so it's in my interest to address that. I have to support a half-dozen platforms and anything that makes that harder is a negative for me. In particular, I have a serious problem if somebody upstream like Macports uses the CF calls in their build instructions. Anything I can do to prevent that is time well spent for me. > The APIs are not "broken", but they are not designed to be used across fork and > clearly warn about that case when you try to do it. Right? Clearly? I wouldn't say that. But regardless, since fork is a pretty standard function, I wold claim that APIs that don't support it are in fact broken. Again, just MHO. -- Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
