| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next


Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

C-ORM: docs, API.

Last 100 entries

Small Success With Go!; Re: Quick message - This link is broken; Adding Reverb To The Echo Chamber; Sox Audio Tools; Would This Have Been OK?; Honesty only important economically before institutions develop; Stegangraphy via PS4; OpenCL Mess; More Book Recommendations; Good Explanation of Difference Between Majority + Minority; Musical Chairs - Who's The Privileged White Guy; I can see straight men watching this conversation and laffing; When it's Actually a Source of Indignation and Disgust; Meta Thread Defending POC Causes POC To Close Account; Indigenous People Of Chile; Curry Recipe; Interesting Link On Marginality; A Nuclear Launch Ordered, 1962; More Book Recs (Better Person); It's Nuanced, And I Tried, So Back Off; Marx; The Negative Of Positive; Jenny Holzer Rocks; Huge Article on Cultural Evolution and More; "Ignoring language theory"; Negative Finger Counting; Week 12; Communication Via Telecomm Bids; Finding Suspects Via Relatives' DNA From Non-Crime Databases; Statistics and Information Theory; Ice OK in USA; On The Other Hand; (Current Understanding Of) Chilean Taxes / Contributions; M John Harrison; Playing Games on a Cloud GPU; China Gamifies Real Life; Can't Help Thinking It's Thoughtcrime; Mefi Quotes; Spray Painting Bike Frame; Weeks 10 + 11; Change: No Longer Possible To Merge Metadata; Books on Old Age; Health Tree Maps; MRA - Men's Rights Activists; Writing Good C++14; Risk Assessment - Fukushima; The Future of Advertising and Surveillance; Travelling With Betaferon; I think I know what I dislike so much about Metafilter; Weeks 8 + 9; More; Pastamore - Bad Italian in Vitacura; History Books; Iraq + The (UK) Governing Elite; Answering Some Hard Questions; Pinochet: The Dictator's Shadow; An Outsider's Guide To Julia Packages; Nobody gives a shit; Lepton Decay Irregularity; An Easier Way; Julia's BinDeps (aka How To Install Cairo); Good Example Of Good Police Work (And Anonymity Being Hard); Best Santiago Burgers; Also; Michael Emmerich (Vibrator Translator) Interview (Japanese Books); Clarice Lispector (Brazillian Writer); Books On Evolution; Looks like Ara (Modular Phone) is dead; Index - Translations From Chile; More Emotion in Chilean Wines; Week 7; Aeon Magazine (Science-ish); QM, Deutsch, Constructor Theory; Interesting Talk Transcripts; Interesting Suggestion Of Election Fraud; "Hard" Books; Articles or Papers on depolarizing the US; Textbook for "QM as complex probabilities"; SFO Get Libor Trader (14 years); Why Are There Still So Many Jobs?; Navier Stokes Incomplete; More on Benford; FBI Claimed Vandalism; Architectural Tessellation; Also: Go, Blake's 7; Delusions of Gender (book); Crypto AG DID work with NSA / GCHQ; UNUMS (Universal Number Format); MOOCs (Massive Open Online Courses); Interesting Looking Game; Euler's Theorem for Polynomials; Weeks 3-6; Reddit Comment; Differential Cryptanalysis For Dummies; Japanese Graphic Design; Books To Be Re-Read; And Today I Learned Bugs Need Clear Examples; Factoring a 67 bit prime in your head; Islamic Geometric Art; Useful Julia Backtraces from Tasks; Nothing, however, is lost with less discomfort than that which, when lost, cannot be missed

© 2006-2015 Andrew Cooke (site) / post authors (content).

Coding Guidelines for C

From: andrew cooke <andrew@...>

Date: Mon, 20 Jun 2011 10:29:38 -0400

I've been back coding in C for a while and want to record some simple rules
that make programs simpler:

1 - Always return a status.  Non-zero is an error.  Always check status on
    return.  On error, goto exit for cleanup.

    So functions should look like:

    int myfunction(blah blah) {
      char *text = NULL;
      void *point = NULL;
      int status = 0;
      if ((status = otherfunction(args here))) goto exit;
      if ((status = yetanother(...))) goto exit;
      if (text) free(text);
      if (pointer) free(pointer)
      return status;

2 - Write allocators and destructors for complex data (structs).  These should
    always take a pointer to a pointer and set the pointer to NULL.
    Similarly, use calloc to allocate data so that pointers are NULL from the
    start).  This follows on from the above - using NULL to indicate that data
    are already freed:

    int alloc_foo(foo **my_foo) {
      int status;
      *my_foo = calloc(1, sizeof(foo));
      if (! my_foo) return MEMORY_ERROR;
      (*my_foo)->counts = calloc(1, 20 * sizeof(int));
      if (! (*my_foo)->counts) return MEMORY_ERROR;
      if ((status = alloc_inner(&(*my_foo)->inner))) return status
      return 0;

    int free_foo(foo **my_foo, status) {
      if (*my_foo) {
        if ((*my_foo)->counts) free((*my_foo)->counts);
        (*my_foo)->counts = NULL;
	status = free_inner(&(*my_foo)->inner, status)
        *my_foo = NULL;
      return status;

3 - Cleanup functions should take status an argument and "make it worse".  the
    the idea here is that you want to call cleanup functions even if there are
    errors, but you don't want to "reset" status to OK (zero) if it was bad.
    In the examples above it's not so clear, but consider, say, releasing a

    int release_db(cnxn *db, int status) {
      if (db_lib_error() && ! status) status = DB_ERROR;
      return status;

    This simplifies the "exit:" code and also allows one-liners when you want
    to do one thing with a database and then release it:

      if ((status = release_db(db, do_db_thing(db, ....)))) goto exit;

4 - Use typedefs for structs:

    typedef struct {
      int my_int;
    } my_struct;

5 - Either namespace with names (and use static functions to avoid clutter
    wherever possible) or namespace with "objects":

    typedef struct self {
      int (*free)(struct self **foo, int status);
    } foo;


Comment on this post