guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The GH interface. (was: Patch for gh.h)


From: Rob Browning
Subject: Re: The GH interface. (was: Patch for gh.h)
Date: 08 May 2001 12:10:26 -0500
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7

Keisuke Nishida <address@hidden> writes:

> What about renaming all public scm_ interface to gh_ and others to gl_?
> Like:

I think I'd prefer to just keep scm_ for public and choose something
else for private - spriv_, priv_, <nothing> or whatever (in the long
run).

Frankly, though another option would be to do what we've done in
gnucash (though there may be good reasons not to).  For many files we
have

  foo.h -- public header containing the publically visible function.
  foo_p.h -- private header containing functions that other .c files need.
  foo.c -- foo source.

Then foo_p.h will include foo.h, and foo.c will include foo_p.h, and
the _p.h headers don't get installed in /usr/include.  An alternate
similar strategies would be to use a include/priv directory, but I
don't particularly like that one during development because it makes
accessing the foo.h foo_p.h pair harder from your editor.

In any case, the _p approach (and guile might want to use _priv.h to
avoid any confusion with respect to the boolean test postfix) has
worked well for us, but I suppose some might find it awkward.

Also, gl_ is probably not a good prefix choice.  It's too confusing
given people's exposure to GL (the 3-D graphics library) which uses
glLineWidth, glClear, etc.

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]