Re: [RFC] export TRUE and FALSE from someplace



Ross McFarland said:
i would have no objections to it so long as
    use Glib qw/TRUE FALSE/
worked as well

would merely require them being both in @EXPORT_OK and %EXPORT_TAGS, which was
the plan.

basically, i was wondering if people thought it was a good idea.  other
constants like G_PRIORITY_* (basically, anything that doesn't fit nicely in
GEnum/GFlags stuff) would be good candidates for the :constants tag.


and it didn't interfere with '-init'.

you'd do Gtk2 separately, e.g.

  use Glib ':constants';
  use Gtk2 -init;


otherwise, we'd have to add code to Gtk2::import to pass the arguments on down
to Glib, which is nasty.



to get ridiculous while we're thinking about constant stuff, would it be
advantageous or desirable to define exportable constants for things like

  use constant GTK_STOCK_OK => 'gtk-ok';

one thing that can keep you guessing is the rules for translating stock macros
to strings...

-- 
muppet <scott at asofyet dot org>



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]