Re: Standalone Pango, take two

[Sergei Steshenko <sergstesh yahoo com>]

--- On Sun, 11/2/08, muppet <scott asofyet org> wrote:

> From: muppet <scott asofyet org>
> Subject: Re: Standalone Pango, take two
> To: "gtk-perl-list gnome org List" <gtk-perl-list gnome org>
> Date: Sunday, November 2, 2008, 8:30 AM
> On Nov 2, 2008, at 11:16 AM, Sergei Steshenko wrote:
> 
> > --- On Sun, 11/2/08, Torsten Schoenfeld
> <kaffeetisch gmx de> wrote:
> >
> >> More importantly even, the loop will also
> automatically map
> >> over any new API we add to Pango, thus indirectly
> changing
> >> Gtk2's API.  Is it better to hardcode the
> stuff that
> >> should be mapped over?
> >
> > [snip]
> >
> >> -Torsten
> >
> > I think the safest approach is to export/map
> _nothing_.
> >
> > If one needs method/data, he/she should explicitly
> prefix it with
> > package name.
> 
> We have to map at least the constructors and some
> constants, or code  
> that worked up to now will break.

[snip]

Yes, exporting was a bad idea in the first place.

Is it possible to do three things:

1) remove each and every default export;
2) create something like DeprecatedFromTheVeryBeginningGtkExports
module that would do the necessary exports for existing applications;
3) remove the DeprecatedFromTheVeryBeginningGtkExports after two-three 
releases ?

Thanks,
  Sergei.