Re: [gtk-list] Re: naming conventions

[Alex Yukhimets <aqy6633 acf5 nyu edu>]

> O> Well, I can't speak for Peter, but I would guess it was partly to
> O> follow the GNU coding standards. The reason given there, if I
> O> recall correctly, is that lower_case_with_underscores is easier to
> O> read than MixedCapsAllRunTogether, especially for non-native
> O> speakers of English.
> 
> It's also easier to use the word-motion commands in various editors.
> And some people (myself included) think that the
> MixedCapsAllRunTogether just looks ugly!
> 

Hi.

Well, tastes differ... 
(You use MixedCapsAllRunTogether as a type names though,
not to mention that it is a Java standard, etc.)

The advantage for you of having lower_case_with_underscores is probably
to have easy visual distinction between "God given" Xlib functions
and your own. But... application programmers may also want to have
this easy distinction - MixedCapsAllRunTogether for standard toolkit
functions and lower_case_with_underscores for their own.

Would it be very difficult to have .h file which would #define
all API functions as MixedCapsAllRunTogether for those who prefer this
way?

Thanks.

Alex Y.