Databases
StackOverflow2013
Postsdbo
POC++ error-codes vs ASSERTS vs Exceptions choices choices :(
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POC++ error-codes vs ASSERTS vs Exceptions choices choices :(
    primarykey
    data
    text
    <p><a href="https://github.com/hsyed/Rubble-DSL/blob/master/include/rbl/common/oid_container.h" rel="nofollow">Code In question</a></p> <p>I have heard (and regurgitated) the C++ exception mantra on both sides of the fence. It has been a while and I just want to centre myself once more, and this discussion is <strong>specific to the code I have linked (or low level classes such as containers)</strong>, and it's dependencies. I used to be a defensive and error_code using C programmer, but it's a tiresome practise and I am programming at a higher level of abstraction now.</p> <p>So I am rewriting a container class (and it's dependencies) to be more flexible and read better (iterators absent atm). As you can see I am returning enumerated error_codes where I know I will test them at call-site. The containers are for runtime building of AST's, initialize and make read-only. The exceptions are their to prevent the container being used naively (possibly by myself in the future). </p> <p>I have exceptions all over the place in this class, and they make me feel dirty. I appreciate their use-case. If I had the choice I might turn them off altogether (Boost uses exceptions a lot, and I am building off Boost, and yes I know they can be disabled, but when in Rome....) . I have the choice of replacing them with error_codes but hey, I will not test them , so what is the point ? </p> <p>Should I replace them with ASSERTS ? What is this bloat people speak off <a href="http://llvm.org/docs/CodingStandards.html#ci_rtti_exceptions" rel="nofollow">[1]</a> <a href="http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml#Exceptions" rel="nofollow">[2]</a> <a href="http://doc.qt.nokia.com/latest/exceptionsafety.html" rel="nofollow">[3]</a>? does every function callsite get extra machinery ? or only those that have a catch clause ? Since I won't catch these exceptions I shouldn't be a victim of this bloatage right ? ASSERTS do not make their way into release builds, in the context of fundamental primitive classes ( -- i.e, containers) does that even matter ? I mean how high are the chances that logic errors would find their way into a final build ? </p> <p>Since we like to answer focused questions, here is mine: <strong>What would you do, and why ?</strong> :D </p> <p><strong>Unrelated Link:</strong><a href="https://github.com/ukplc/rbl-rpc/blob/master/include/rpc/common/rpc_errors.h" rel="nofollow">Error codes and having them piggy backing in an exception.</a></p> <p><strong>edit 2</strong> in this particular case the choice is between ASSERTs and exceptions, I think exceptions make the most sense, as I mentioned above, the container is read only after initialisation, and most of the exceptions are triggered during initialisation.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USHassan Syed
    1. USHassan Syed
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POC++ error-codes vs ASSERTS vs Exceptions choices choices :(
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POC++ error-codes vs ASSERTS vs Exceptions choices choices :(
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POC++ error-codes vs ASSERTS vs Exceptions choices choices :(
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIt is possible to make a class that will hold an error code and throw if the error code is not checked. I've been meaning to write up the exact process for a long time now.
      singulars
      1. POC++ error-codes vs ASSERTS vs Exceptions choices choices :(
      1. USMark Ransom
    2. COI don't feel like reading 364 lines of code. Could you tell us the relevant line numbers?
      singulars
      1. POC++ error-codes vs ASSERTS vs Exceptions choices choices :(
      1. USAndrew Shepherd
    3. CO@Andrew exception emitions have the word "throw" in them, and the only strings (the red looking stuff) are exception messages :D
      singulars
      1. POC++ error-codes vs ASSERTS vs Exceptions choices choices :(
      1. USHassan Syed
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload