On Fri, Sep 23, 2011 at 13:29, Masaaki Aoyagi <masaakiaoyagi@...> wrote:
>>> * Change file name to like 'rbvte-terminal.c'
>> Is changing file names really needed?
>> Not that I care much but it makes following project history harder
>> when all files are suddenly renamed at some point.
> Changing file names is not really needed for this migration.
> But yagi_gnome includes feature to generate source files from GIR, and
> it needs naming rules.
> So, I would like to change file names.
I’m not happy about having to change the names, but I think the naming
should follow that in the relevant library that we are wrapping, and
if we can get things for free, then changing the names of files is
definitely worth it.
On the C side, Atk, GIO/GLib/GObject, goocanvas, GStreamer, Gtk,
GtkSourceView, and Vte all use the atkaction.c style.
Gdk-pixbuf, Pango, librsvg use the gdk-pixbuf-animation.c style.
Poppler is written in C++ and uses the PopplerCache.cc style.
(The gdk_pixbuf2 library should really have been called gdk-pixbuf2,
but that’s beside the point.)
My opinion is that we should follow the first style, namely
atkaction.c. If there is any value in adding a “rb” prefix, then
fine, call it rbatkaction.c. I’ve never seen the value of adding yet
another prefix, however, so I didn’t do so for gio2.
Whatever we decide, I think that we should have one rule that applies
to all files in the project.