Max Kellermann <[EMAIL PROTECTED]> wrote: > On 2008/09/02 05:30, Eric Wong <[EMAIL PROTECTED]> wrote: > > I hate CamelCase, too; but can we avoid reusing the struct names > > as the variable name (e.g. struct foo *foo)? > > > > It makes things like searching for and renaming variables > > more difficult than they need to be. > > Most of the time, "foo" is the best name coming to my mind for a > variable of the type "struct foo" .... I agree it's confusing, but I'm > bad at thinking about names, does anybody have a good idea, which is > understandable and readable? (not one-letter names like "struct foo > *f", and no "struct foo_struct" please).
I've already merged your tag stuff with "struct mpd_tag" since that resembles the old name: "MpdTag" Not sure what to do with "struct client", "struct mpd_client" maybe? "struct foo *f" is alright in small doses for iterators and temporary variables. "struct foo_struct" is never acceptable. -- Eric Wong ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
