Re: Function prefixes

[Behdad Esfahbod <behdad cs toronto edu>]

On Mon, 19 Sep 2005, Bruno Haible wrote:

> > So, hereby, I suggest using "giu_" instead.  How's that?
>
> Well, giulia is the roof project for a set of separate libraries and
> programs. To stress the fact that they are _separate_ and that we don't want
> a big ICU-like thing, I'd prefer to have a prefix for libglocale, a prefix
> for the Unicode regex library, a prefix for the GNOME configuration panel, etc.
>
> So I'm inclined to use "glc_" for libglocale.

I was thinking about going the glib way.  glib is a set of three
libraries, called gthread, gobject, and glib (everything else).
They all use the "g_" as the first-level prefix.  gobject uses
the "g_object_" prefix, gthread uses "g_thread_", and there are
various subsystems in the catch-all library, like g_unicode_,
g_key_file_, g_mainloop_, etc...

So, my proposal is to use the giu_ prefix for all libraries
developed as part of the giulia project, and use a second prefix
to identify the subsystem and probably the header files and
shared objects that the function is defined in.  I like the idea
for it to look like an integrated set of libraries that share the
same namespace, but completely isolated in there.  This also
avoids the problem of having to come up with names for different
libraries in giulia.  So maybe we should rename glocale to
giulocale too, what do you think?  I'm trying to avoid the g
prefix in favor of giu.  The g prefix is overly reused by the GNU
project, GNOME project, and glib.

This reminds me that we need to settle on the header-file naming
and installation scheme too.  This is a classic read:

  http://www106.pair.com/rhp/parallel.html

and the scheme is common in core GNOME libraries, with not much
problem so far.


> Bruno


--behdad
http://behdad.org/