Re: Re: Enums, flags and ::

Relax, the CS are in CVS now :) ----- Original Message ----- From: "Jeremy Johnstone" <phpdev@gmail.com> To: "Steph Fox" <steph@zend.com> Cc: "Andrei Zmievski" <andrei@gravitonic.com>; "PHP-GTK gen" <php-gtk-general@lists.php.net>; "PHP-GTK dev" <php-gtk-dev@lists.php.net> Sent: Thursday, October 27, 2005 7:27 AM Subject: [PHP-GTK-DEV] Re: [PHP-GTK] Re: Enums, flags and :: Honestly I have to agree with you gtk::main() "looks" better, but from a logical standpoint I think it is actually not as clear as Gtk::main(). It's a subtle difference, but having the first letter uppercase makes it a lot clearer that it is a static class method rather than a function. On the other point, please remember that you aren't forced to use Gtk::WHATEVER for your own code if you absolutely don't want too. It's not something I would do, but you are of course free to do something like the following: define("GTK_WHATEVER", Gtk::WHATEVER); The flip side is that it's not feasible to do the reverse (atleast not easily), so it's more flexible doing it the way we are. I also feel very strongly about segregating the constants because it makes looking them up so much easier. If I am looking for all Gtk constants it much easier this way than having to grep all the hundreds of global constants for things starting with GTK_. -Jeremy On 10/26/05, Steph Fox <steph@zend.com> wrote: > > > Well, it is a class after all. What's wrong with Gtk as a class name? > > I'd rather we choose one case standard for class names and stick to > > it. Let's not be inconsistent. > > > <sigh /> > > I better not run for any kind of candidacy this year, eh? > > - Steph > > -- > PHP-GTK General Mailing List (http://gtk.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- --------------------------- Jeremy Johnstone http://www.jeremyjohnstone.com jsjohnst@php.net