Re: To gh_ or not to gh_?

[Rob Browning]

Neil Jerram <address@hidden> writes:

> That's a strange assertion.  Why do you say this?

Maybe he means they should always be hidden behind a C api?  In
general, especially for a "portable generic API", I tend to agree.

You can do a

  typedef struct _foo Foo;

  Foo bar();
  int baz(Foo x);

in the public header, and then a

  struct _foo {
    ...
  };

in the .c file.

Makes sure you'll always be able to change the implementation without
impacting user code...

-- 
Rob Browning <address@hidden> PGP=E80E0D04F521A094 532B97F5D64E3930