This is a typical "me too", but I post anyway to emphasize two things.
Brian wrote:
>This is the part that worries me the most. We will need to get Inline
>past beta to "Release" quality relatively soon.
So far my impression is that Inline development is moving really fast right
now. That is very good. We don't want to lose that.
Having Inline as part of the Perl distribution has tremendous potential,
simply because it is such a valiable module, both to programmers and to
Perl as a language. This is because, like Paul Wilt mentioned, it is now
possible for mere mortals to actually tie e.g. C to Perl. Pre Inline this
was technicaly possible. Now it is practically possible. The ease of use
improves the Perl language.
So losing the opportunity would be a bad thing, but not a very, very bad
thing since Inline will be available anyway, just not as conveniently.
Would there be any problems with the dual code base scenario that Eric Kort
described? I don't really see any right now.
/J
------ ---- --- -- -- -- - - - - -
Johan Lindström Boss Casinos
Sourcerer [EMAIL PROTECTED]
http://www.bahnhof.se/~johanl/
If the only tool you have is a hammer,
everything tends to look
like a nail
