Cart
[Home] [By Thread] [By Date] [Recent Entries]
To summarize some off-line discusions, it's not "necessary" to use a new exception model due to any MT isues in C++ program; state kept on the stack, easily accessible to applications, suffices for reasonably written chunks of code. As in Java, so in C++. (Although historically it goes the other way around ... C++/MT/Exceptions illuminated the design of Java exceptions, along with experience in other languages that offered OO, MT and exceptions well before C++ got its clue!) - Dave "Mark D. Anderson" wrote: > > > I'll confess I didn't quite notice any MT issues in that post, but as you > > stated it was really a "what Parser/InputSource is in use" issue that > > isn't MT-specific at all. > > > > I can't see a way confusion could arise there unless one parser callback > > needs to invoke some other parser, and is sloppy about letting exceptions > > from that invocation appear as if they were exceptions from the current > > invocation. There are always ways to create bugs if code isn't careful. > > if i have a single catch which is "above" multiple simultaneous parsing > activities, then how can i determine from the exception object alone > which parser is involved? or is the answer to not do that? > > -mda xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To unsubscribe, mailto:majordomo@i... the following message; unsubscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
