NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
questions (Score:1)
Is there an appropriate public forum to ask questions about Artistic 2? Is there a FAQ?
You mention answering questions [blogs.com]. Is there any record of the question and answer session?
I ask, because the mailing list you mentioned in your announcement has been inactive for 4 years. And the questions asked in the comments [perl.org] section of your announcement have gone unanswered. As have the questions I asked [google.com] on perl6-internals mailing list back in October.
I don't understand the need for the compilation copyright. But I
Re: questions (Score:1)
Me too... (Score:1)
For example, we have Perl modules now that link to GPL or LGPL libraries. I gather current this is fine because we create these modules as seperate programs and they never really get "linked" as such.
But if the new Perl 6 world allows compilation (as I gather it does) what does this mean for the dozens of modules that wrap GPL or LGPLed libfoo modules.
Is there a giant Perl 6 Licensing FAQ somewhere?
I don't understand. (Score:1)
Re: I don't understand. (Score:1)
No, there isn't a fundamental problem with public domain code and AL2. Public domain code can always be included in anything. (That's the whole point of the public domain.)
I think you're referring to the problem with having Pugs be public domain and then become the production implementation of Perl 6? The problem there is not that we can't include public domain code in AL2 code, the problem is that if all of Perl 6 (or even 90% of it) is available as public domain, then there's nothing to stop an unscrup