6 ms·
Maybe my experience is atypical but RTTI and exceptions are features of C++ that I never see used in real-world C++ almost regardless of the application. When I
by jandrewrogers 10y ago
Maybe my experience is atypical but RTTI and exceptions are features of C++ that I never see used in real-world C++ almost regardless of the application. When I have seen them used, it is by people new to C++ that haven't fully figured out the common development idioms of the language yet.
- jlarocco 10y agoI've never seen RTTI use in production code. Even with modern C++, RTTI almost always adds too much runtime overhead and negative performance impacts. Most importantly, it's usually a sign of bad design. My experience with exceptions is different, though, and I see them used quite a bit. It depends a lot on the age of the code base and the group working on it. Old code is less likely to use them, and developers with a heavy C background, or a lot of pre-C++98 experience are less like to use them. Except for maybe some tiny embedded systems (like microcontrollers), the overhead of exceptions isn't that bad any more.
- vvanders 10y agoMy experience has been no rtti and no exceptions. Quite a few compilers generate rtti if you use exceptions. Generally I haven't found any error handling solution where exceptions provided superior semantics. The lack of checking means that you can catch more bugs with enum error codes + switch and Wall.
- fauigerzigerk 10y agoThe strange thing about exceptions in C++ is that they make ubiquitous use of RAII a necessity, but at the same time they must not be thrown in destructors. And then C++ exceptions don't come with a stack trace that makes quick and dirty exceptions based code so convenient in Java or C#. I was never a principled opponent of exceptions, but I find myself removing them from more and more code the more thoroughly I think about all the possible error states of code that should really be robust.
- tibbetts 10y agoGetting a stack trace on Linux or Windows is pretty straightforward. It is too bad it is not standardized but the large projects I work on have stack traces
- maxlybbert 10y agoI don't find it weird that exceptions shouldn't be thrown from destructors. I remember being surprised when I learned that rule, but the reasoning seems sound to me: what can you do when the cleanup failed? Clean up harder?
- fauigerzigerk 10y agoThe short answer is that action B may depend on whether or not action A was able to finish successfully, including any cleanup.
- maxlybbert 10y agoThe official reason destructors are discouraged from throwing exceptions is that one reason destructors get called is that something already threw an exception, and there is currently no way to handle two exceptions in flight at once, so in that case the process gets killed. It's also true that with more experience, we've figured out that cleanup code is special. When I throw an exception during normal processing, I want to abandon what I'm doing. But if I discover that one step of a destructor cannot be completed, I do not want to abandon the rest of the cleanup. If I throw an exception in a destructor, I can't come back later to finish any remaining steps. And, as I asked earlier, if I throw an exception because I can't close a file, what do I expect the exception handler to do? I guess it could try closing the file again, but I'm not going to hold my breath on that working. Perhaps the file is on a network share and the network's gone down. Perhaps closing the file will involve writing some cached data to disk, but the disk is full. In my experience, in this case your only real options are "ignore it, either because there's nothing you can do or because you're already dealing with an exception and you've simply discovered another symptom of the original problem" or "kill the program because there is no hope." You can log the fact that a step failed, but remember that it's possible for logging to fail, if the disk is full.
- deleted 10y ago[deleted]
- MaulingMonkey 10y ago> I've never seen RTTI use in production code. I have, but it's almost never the extremely limited built-in RTTI. > Except for maybe some tiny embedded systems (like microcontrollers), the overhead of exceptions isn't that bad any more. Big caveat here: Unthrown / rare exceptions aren't that bad. I ran into a bug with the windows 8 touch APIs, where the pointer ID for a given finger would become invalid just before we recieved the "pointer up" notification if you pawed at the screen in just the right way. This manifested as an exception being thrown when querying the pointer position - which, of course, wasn't caught, meaning pawing at the screen just right crashed the program. Catching the exception stopped it from crashing, at least. But the framerate would tank if you pawed at the screen, from exception handling overhead alone. I've come to frown on exceptions in C++, for production gamedev. Everything else is using error codes anyways, why add a second error handling style into the mix? Your callbacks may be invoked from third party C, which you can't safely throw across, or C++ built with exceptions disabled, which you also can't safely throw across. Heck, just building with exceptions enabled can be difficult - I could not link against some of the C++ PS4 libraries without matching many of their build settings - including having exception handling disabled. ...I resorted to alternative options for handling failed unit tests.
- pjmlp 10y agoGame engine middleware like Unreal, Qt, MFC, VCL. The difference being that they created their own version.
- vvanders 10y agoLarge difference there is that in those systems you opt-in and only pay for it in the classes you want(which is more in line with C++). In the case of Unreal we used it to extend the RTTI system to to more things than just isA(). Stuff like member properties(editor hints in window), serialization(network & disk) and stuff you'd use C# attributes for.
- pjmlp 10y agoI guess C++ would have been more well served by having static RTTI, but if it comes will be only on C++20 most likely, although type traits and template meta-programming already get us half way there. However when I look to such examples, I am quite happy to spend most of my time on JVM/CLR lands. It is not the meta-programming as such, rather the decltype, trailing return types and SFINAE tricks that put me off.
- maxlybbert 10y agoI've seen very little RTTI, but I've seen it. There are a large number of programmers who use C++ "because it's fast," and they've heard RTTI and exceptions (and virtual function calls, ...) are slow, so they avoid those features. But the common implementations for RTTI and exceptions have improved. They're much faster than they used to be. The performance problem isn't that they're slow, but that their performance is unpredictable. Not terribly unpredictable, but unpredictable enough to rule them out in real time code. But for most everyone else, they're plenty fast. Or, put another way, if RTTI and exceptions make your project noticeably slower, you're doing too many dynamic_casts and/or throwing too many exceptions. At this point the question should be "does this lead to a good design?" and not "does my gut think it's fast enough?"
- erichocean 10y ago> exceptions are features of C++ that I never see used in real-world C++ Well, I use exceptions in exactly one situation: my request handlers on the server are all one-shot, transactional, and throwing anywhere unwinds to the top of the stack, aborts the transaction, and results in an error message being returned to the caller. For that specific use case, I find exceptions cleaner than any other approach I've tried. Otherwise, I avoid them as well.
- pmelendez 10y agoDo you work for a Foreign Exchange company? We used it exactly for the same scenario at a previous employer.
- erichocean 10y agoI do not, but thanks for the info I'm not the only one!
- pif 10y ago> RTTI and exceptions are features of C++ that I never see used in real-world C++ Regarding exceptions, in my experience it depends a lot of the cultural background of the developers: Unix developers tend to use them, Windows developers don't.
- 72deluxe 10y agoHang on, from all these comments we are saying that nobody ever does dynamic_cast ???
- Asooka 10y agodynamic_cast doesn't work across .sofiles loaded with dlopen: https://stackoverflow.com/questions/23383102/dynamic-cast-troubles-over-shared-libraries https://stackoverflow.com/questions/23383102/dynamic-cast-tr... I've seen it first hand crap itself on Mac OS X. The gist of it is that if you have a plugin architecture, you can't pass an object allocated in one plugin to another and have the latter do a dynamic_cast. For the same reason exceptions thrown in a plugin can't be caught in another unless the type is defined in the host binary. I.e. suppose the main application has: class HostException { virtual ~HostException() {} }; class FooInterface { virtual void doBar()=0; }; Then inside plugin A you do try { foo->doBar(); } catch (HostException& ex) { // stuff } where foo was allocated in plugin B. Then, // in plugin B class FooImpl : public FooInterface { virtual void doBar() override; }; class MyException : public HostException { virtual ~MyException() {} }; void FooImpl::doBar() { throw HostException(); // should be just fine throw MyException(); // here be dragons } For that reason in places where we call foreign code that we know could throw we just do a blanket catch(...) and bail out on any exception. Similarly we don't rely on dynamic casts at all anywhere, we use our own type system. The OOP features of C++ are fine for small toy programs but ironically they break when you try to use them for actual large ones that would benefit the most from them. Stick to virtual functions, static and reinterpret casts and nothing else.
- p0nce 10y agoIn my experience not using exceptions in C++ is more a generational thing than anything. Older foxes don't use them because they don't use RAII systematically either.