Re: Removing defs
| From: | Steph Fox | Date: | Sat, 08 Jul 2006 02:28:36 +0000 |
| Subject: | Re: Removing defs | ||
| Groups: | php.gtk.dev | ||
| Request: | Send a blank email to php-gtk-dev+get-3205@lists.php.net to get a copy of this message | ||
erm, what I think I'm trying to say goes something like 'it was put there as a convenience, so why do we think we need to lose it?'
come to that, why not leave two potential constructors? - I realise it's 'different' but then so is filter... it's effectively just a struct that happens to be a child class...cweiske Fri Jun 30 23:00:43 2006 UTC Modified files:I prefer that we mess with .defs files as little as possible, since it will reduce any potential merge conflicts when we merge in 2.8.x .defs. Why not just 'ignore' this function? -Andrei -- PHP-GTK Development Mailing List (http://gtk.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php/php-gtk/ext/gtk+ gtk.defsLog: Removing GtkTreeModel::filter_new, since we already have a GtkTreeModelFilter constructor