Re:Measuring execution performance of C++ exceptions vs. err...
by saurik on Monday January 09, 2017 @06:51AM
(#13355664)
That result object is implemented in the same manner to an error code: you are burning cycles and registers on something that usually doesn't come up... all so you can clutter your code with what effectively amounts to a manual implementation of exception handling :/.
[ Parent
| on HN ]
Re:Measuring execution performance of C++ exceptions vs. err...
by arcticbull on Monday January 09, 2017 @07:02AM
(#13355711)
That's fair, though in my opinion it's more important to be clear and explicit in what's happening both for your own sake and for your future co-workers so they can understand what's happening and why than worrying about some minor (per the article) performance issues.
Re:Measuring execution performance of C++ exceptions vs. err...
by nick_ on Monday January 09, 2017 @11:06AM
(#13357306)
That's what exceptions are for. They are a tool that _can_ be used to cut down on noise in code. Being clear and explicit about everything will leave your code looking like an implementation of the STL. The art of programming is partly about achieving a good signal-to-noise ratio.