Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm a little horrified by all the recommendations for a goto statement!</p> <p>I have found that the use of goto leads to confusing code which is more likely to give rise to programmer errors. My preference now is to avoid its use altogether, except in the most extreme situations. I'd almost never use it. Not because of academic perfectionism, but because a year or more later it always seems more difficult to recall the overall logic than with the alternative I will suggest.</p> <p>Being one who loves to refactor things to minimize my option to forget stuff (like clearing a pointer), I'd add a few functions first. I'll presume it's likely that I would be reusing these quite a bit in the same program. Function imalloc() would do the malloc operation with the indirect pointer; ifree() would undo this. cifree() would free memory conditionally.</p> <p>With that in hand, my version of the code (with a third arg, for sake of demonstration) would be like this:</p> <pre><code>// indirect pointer malloc int imalloc(void **mem, size_t size) { return (*mem = malloc(size)); } // indirect pointer free void ifree(void **mem) { if(*mem) { free(*mem); *mem = NULL; } } // conditional indirect pointer free void cifree(int cond, void **mem) { if(!cond) { ifree(mem); } } int func(void **mem1, void **mem2, void **mem3) { int result = FALSE; *mem1 = NULL; *mem2 = NULL; *mem3 = NULL; if(imalloc(mem1, SIZE)) { if(imalloc(mem2, SIZE)) { if(imalloc(mem3, SIZE)) { result = TRUE; } cifree(result, mem2); } cifree(result, mem1); } return result; } </code></pre> <p>I prefer to have only one return from a function, at the end. Jumping out in between is quick (and in my opinion, kind of dirty). But more significantly, allows you to easily bypass associated cleanup code unintentionally.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat is the best way to free memory after returning from an error?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdigijock
    1. USdigijock
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COThis function leaks memory if it returns FALSE and frees memory when it returns TRUE, not what the questioner asked.
      singulars
      1. PO
      1. USDour High Arch
    2. COCorrected the typo - the cond comparision should have been (!cond).
      singulars
      1. PO
      1. USdigijock
    3. CODour High Arch - It would be nice if you would retract the comment since it is incorrect. The basic scheme I presented does in fact work quite well, does not leak, and does not return invalid pointers.
      singulars
      1. PO
      1. USdigijock
 

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