> WHOA! > > I _am_ telling you I think exceptions are faster than other control > structures _In_ _Some_ _Cases_. > > But you can just think about that. Or not. I'm happy to explain & > clarify if I am unclear. But I am not here to tell you what to do and > prove why you should do it. >
It went like this: Mark asked: >But for safety critical projects, the no rtti, no exceptions rule >is pretty common isn't it? Not sure if it's justified or not, but >very common from what I hear. Something to do with code verification, >provability? Not that that gives any lessons for application code >in other domains, necessarily. I explained why no exceptions in FAA life critical code. You then respond with: > Well, you get one exception at a time, much like you > get one if or goto or return at a time. No different than jumps. at which point saying exceptions are "No different than jumps" is sort of a red flag. You then go on in that same email to use the example of using exceptions to read a file until EOF. Which wouldn't be allowed in FAA code. Whether exceptiosn are faster than normal constructs in any particular case could be objectively measured. But the original question was why no exceptions in cases like flight code and so on. And in that case it's not just about being fast, its about about being provably fast no matter what. Greg _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
