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

C[omp]ute

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

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; Article on Didion; Cost of Living by City; British Slavery; Derrida on Metaphor; African SciFi; Traits in Julia; Alternative Japanese Lit; Pulic Key as Address (Snow); Why Information Grows; The Blindness Of The Chilean Elite; Some Victoriagate Links; This Is Why I Left StackOverflow; New TLS Implementation; Maths for Physicists; How I Am 8; 1000 Word Philosophy; Cyberpunk Reading List; Detailed Discussion of Message Dispatch in ParserCombinator Library for Julia; FizzBuzz in Julia w Dependent Types; kokko - Design Shop in Osaka; Summary of Greece, Currently; LLVM and GPUs; See Also; Schoolgirl Groyps (Maths); Japanese Lit; Another Example - Modular Arithmetic; Music from United; Python 2 and 3 compatible alternative.; Read Agatha Christie for the Plot; A Constructive Look at TempleOS; Music Thread w Many Recommendations; Fixed Version; A Useful Julia Macro To Define Equality And Hash; k3b cdrom access, OpenSuse 13.1; Week 2; From outside, the UK looks less than stellar; Huge Fonts in VirtualBox; Keen - Complex Emergencies; The Fallen of World War II; Some Spanish Fiction; Calling C From Fortran 95; Bjork DJ Set; Z3 Example With Python; Week 1; Useful Guide To Starting With IJulia; UK Election + Media; Review: Reinventing Organizations; Inline Assembly With Julia / LLVM; Against the definition of types; Dumb Crypto Paper; The Search For Quasi-Periodicity...; Is There An Alternative To Processing?; CARDIAC (CARDboard Illustrative Aid to Computation); The Bolivian Case Against Chile At The Hague; Clear, Cogent Economic Arguments For Immigration; A Program To Say If I Am Working; Decent Cards For Ill People; New Photo; Luksic And Barrick Gold; President Bachelet's Speech; Baltimore Primer; libxml2 Parsing Stream; configure.ac Recipe For Library Path; The Davalos Affair For Idiots; Not The Onion: Google Fireside Chat w Kissinger; Bicycle Wheels, Inertia, and Energy; Another Tax Fraud; Google's Borg; A Verion That Redirects To Local HTTP Server; Spanish Accents For Idiots; Aluminium Cans; Advice on Spray Painting; Female View of Online Chat From a Male; UX Reading List; S4 Subgroups - Geometric Interpretation; Fucking Email; The SQM Affair For Idiots; Using Kolmogorov Complexity; Oblique Strategies in bash; Curses Tools; Markov Chain Monte Carlo Without all the Bullshit; Email Para Matias Godoy Mercado; The Penta Affair For Idiots; Example Code To Create numpy Array in C; Good Article on Bias in Graphic Design (NYTimes); Do You Backup github?

© 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;
      ...
    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
    database:

    int release_db(cnxn *db, int status) {
      db_lib_release(db);
      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;

Andrew

Comment on this post