After 0.44 goes out, the next big push will be for Inline 0.50.

The theme of 0.50 is "restructuring".

The basic functionality will not change, but the way that Inline is
packaged and distributed will be reworked.

1) The Inline.pm module will be reduced to less than 50 lines of code.
   The bare minimum needed to support pre-compiled Inline extension
   modules like Tie::GHash. It will be distributed on CPAN as
   "Inline-Stub".
2) The rest of the current Inline.pm module will be put into a module
   called Inline::Devel. You'll need this to do the things you normally
   do with Inline. It will be distributed as "Inline-Devel".
3) Inline::C will be distributed in it's own distribution called
   "Inline-C".
4) Finally, (and this is the important part), the *distribution* known
   as "Inline" will become a very big distribution containing:
   A) Inline-Stub
   B) Inline-Devel
   C) Inline-C
   D) Inline-CPP
   E) Inline-Insh
   F) Inline-Filters
   G) Inline-Struct
   H) YAML
   I) Term-Shell (the base class for Inline-Insh)
   J) Inline-FastParser ???
   K) Inline-NativeParser ???
   The distribution will be smart. It will know how to correctly upgrade
   each component. It will also let you choose which components you want
   to install.

If this turns out to be successful we may start bundling other popular
ILSMs with Inline.

Cheers, Brian  


Reply via email to