Fellow modulars, What do you think? -- Johan
Hello, Inline.pm version 0.30 has just been released, along with Inline::CPR. Inline::Python and Inline::CPP (by NEILW) will follow very shortly. I am writing this to make aware my intentions and concerns regarding the Inline namespace. Version 0.30 provides a clear API for adding new language support. It also provides documentation for doing so. I would like to see Perl glued to as many languages as is useful. I have intentions to start exploring Java, Fortran, Ruby, and bash. I have hopes that this will become a community project. I have obtained the [EMAIL PROTECTED] mailing list for that purpose. My concern is that people will want to take over namespaces like Inline::COBOL without consulting the Inline community. I would ask that the moderators of [EMAIL PROTECTED], please make sure that people requesting Inline:: namespaces, have obtained the blessing of the Inline community. Please note that Inline support modules may be distributed under different namespaces, and still work with Inline.pm. In other words there can be more than one implementation of Lisp for Inline. But I want to retain the right to insure that the author of the Inline-Lisp distribution is working with the rest of the Inline community. Here is what I wrote in Inline-API.pod: The Inline Namespace: Inline.pm has been set up so that anyone can write their own language support modules. It further allows anyone to write a different implementation of an existing Inline language, like C for instance. You can distribute that module on the CPAN. If you have plans to implement and distribute an Inline module, I would ask that you please work with the Inline community. We can be reached at the Inline mailing list: [EMAIL PROTECTED] (Send mail to [EMAIL PROTECTED] to subscribe). Here you should find the advice and assistance needed to make your module a success. The Inline community will decide if your implementation of COBOL will be distributed as the official Inline::COBOL or should use an alternate namespace. In matters of dispute, I (Brian Ingerson) retain final authority. (and I hope not to need use of it :-) Actually [EMAIL PROTECTED] retains the final authority. But even if you want to work alone, you are free and welcome to write and distribute Inline language support modules on CPAN. You'll just need to distribute them under a different package name. ---------------------------------------------------------- Sincerely, Brian Ingerson <[EMAIL PROTECTED]> -- perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf ("Just Another %s Hacker",x);}};print JAxH+Perl'
