I wonder if this site is really out of date as the dates at the top indicate?
http://smoke.perl6.org/report
If so, is there working version of this report?
Gabor
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #128457]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128457 >
If a Perl 6 module and a Perl 5 module are used in the same class, using that
class fails
Tadeusz SoĊnierz wrote [off-list]:
On 29-07-2010 14:37:54, Darren Duncan wrote:
Now that, with Rakudo Star, it is relatively straightforward to
install and use Perl 6, I'm wondering about the next step.
I want to start writing and distributing Perl 6 modules in an easily
installable bu
Now that, with Rakudo Star, it is relatively straightforward to install and use
Perl 6, I'm wondering about the next step.
I want to start writing and distributing Perl 6 modules in an easily installable
but non-bundled manner, much as how one can do so today with Perl 5 modules.
What i
> I tried to read the Synopse S11 and how modules will be working in Perl
> 6: to be honest I still not really anderstand it :)
What may help me is to know where Perl 6 modules are to be placed in the
module taxonomy used in the module calculus paper below.
> To develop the classbo
Hi,
In the last few months, I tried to anderstand better Roles aka statefull
traits, so I read differents traits papers about it. From the same
research group, I also read about classboxes and found the concept
interresting, particulary when combined with traits (roles).
Please note that I am not
At 7:39 PM +0800 7/18/05, Gav wrote:
What would be the changes required to write this a Perl 6 file, my guess is
:-
#!/usr/bin/pugs
use v6;
but I don't know about the rest of it.
I'd like to get this sorted first and then write a test perl6 module and use
that in my test perl 6 script. The
- Original Message -
From: "Stevan Little" <[EMAIL PROTECTED]>
Subject: Re: Perl 6 Modules
| Gav,
|
| Welcome aboard. You might also want to hop onto the #perl6 channel over
| at irc.freenode.net it is where many of use spend way too much time,
| and a great place for
Modules
out there so why are they not in here, are all the v6 modules included
in
Pugs? - Can Perl6 modules now be submitted to CPAN?
CPAN has no real rules, so you can submit a Perl 6 module if you like,
but it will likely be frowned upon. Currently all the working Perl 6
modules are inside
From: "Nathan Gray"
| A good starting place is:
|
| http://svn.openfoundry.org/pugs/docs/other/porting_howto
Looks good ,thanks.
For those of you that have been here a while I suspect you do not notice,
but to me there seems to be no structure, no definitive place where one can
go and find e
ace is:
http://svn.openfoundry.org/pugs/docs/other/porting_howto
> I have downloaded PXPerl for Windows (which seems a bit broken to me atm)
> and
> wanted to start writing some (fairly basic to start with) Modules.
>
> As Perl 6 Modules are to work with Perl 5 it makes sense for me
some (fairly basic to start with) Modules.
As Perl 6 Modules are to work with Perl 5 it makes sense for me to learn
this straight off.
Apologies for intruding on this list, but I see no perl6-modules list
anywhere and only
brief mentions of v6 Modules in places.
You are all doing a great job
ly
v5.8.1".
8. Had an IRC chat on names for Perl 6 modules; I'll post something
about this to the email list in a little while, following what came
out of that (suggesting the creation of a FAQ-type or standards
committee recommendation type document).
Finally, I expect to add+commit
On Sun, Mar 06, 2005 at 16:40:46 -0800, Darren Duncan wrote:
> I'll start showing up on IRC soon, though I have to find a good Mac
> OS X client for IRC first (I'm still used to email as a primary
> communication medium).
I'm very happy with colloquy (http://colloquy.info). You can
probably get
or now, since it has less
need to stand on its own. I will move just the code over to Perl 6,
and include a comment to look at the Perl 5 version for the user
documentation. Documentation will be copied to the Perl 6 version
when there is good reason to do so.
I also have some input of my own
On Sat, Mar 05, 2005 at 03:25:55PM -0800, Darren Duncan wrote:
> I wish to help out the development of Perl 6, initially running under
> Pugs, by supplying test code of sorts, written in Perl 6, that we
> would attempt to run under Pugs (and eventually Parrot) to ensure
> that it works correctly
to give in this
department would surely be appreciated, whether is be a complete port
of your module, or something smaller.
Considering the Apocryphon question on a CPAN for Perl 6 modules, I
will conform by initially naming my modules into the "Perl6::lib"
namespace; they will have th
t none of my modules will work
until at least version 6.28, since they are object oriented. At the
same time, I don't do anything particularly fancy, so I probably
don't need the features pending subsequent major releases.
Considering the Apocryphon question on a CPAN for Perl 6 modules,
Kirrily 'Skud' Robert [mailto:[EMAIL PROTECTED]] said:
>
> My main purpose with perlmodstyle was to give us a starting
> point for a Perl 6 style guide, in time for the Great Rewrite
> that's likely to happen with most of CPAN.
>
I have some raw material that may be useful (and I do mean raw).
O
In perl.perl6.stdlib, you wrote:
>
>Something like perlstyle and perlmodstyle for perl 5 then?
My main purpose with perlmodstyle was to give us a starting point for a
Perl 6 style guide, in time for the Great Rewrite that's likely to
happen with most of CPAN.
K.
--
Kirrily 'Skud' Robert - [EM
On 8/25/01 1:51 PM, Kirrily Robert wrote:
> In perl.perl6.stdlib, you wrote:
>> Er, okay, well scratch that example then :) But my point still stands: I
>> think Perl 6 should have some sort of guidelines in this area, even if
>> they're only a codification of what "the majority" of Perl authors
On Sat, Aug 25, 2001 at 09:40:05AM -0400, John Siracusa wrote:
> On 8/25/01 5:12 AM, Johan Vromans wrote:
> > John Siracusa <[EMAIL PROTECTED]> writes:
> >> If you ask any Java programmer which is "correct", myJavaMethod() or
> >> My_Java_Method(), I think you'll get a straight answer.
> >
> > Fr
In perl.perl6.stdlib, you wrote:
>
>Er, okay, well scratch that example then :) But my point still stands: I
>think Perl 6 should have some sort of guidelines in this area, even if
>they're only a codification of what "the majority" of Perl authors do.
Yes. See also "perldoc perlstyle" and the
On 8/25/01 5:12 AM, Johan Vromans wrote:
> John Siracusa <[EMAIL PROTECTED]> writes:
>> If you ask any Java programmer which is "correct", myJavaMethod() or
>> My_Java_Method(), I think you'll get a straight answer.
>
> From experience I can assure you this is not the case. There are a
> couple o
John Siracusa <[EMAIL PROTECTED]> writes:
> If you ask any Java programmer which is "correct", myJavaMethod() or
> My_Java_Method(), I think you'll get a straight answer.
>From experience I can assure you this is not the case. There are a
couple of (independent and mutual inconsistent) style gui
On 8/24/01 11:52 PM, John Siracusa wrote:
> I mentioned this on another list, and I thought I'd bring it up here as
> well. I think NeXT-style "bundles" offer an interesting solution for
> keeping several versions of a single library installed at the same time,
> with well-defined major/minor ver
I just subscribed, so forgive me if this has been covered before (I haven't
read all of the archives yet)
STYLE:
> There should be tools, guidelines and processes to assist authors in writing
> quality modules. See also [EMAIL PROTECTED]
> Specifically:
> Style guide
> Naming guidelines
I kno
On Tue, 14 Aug 2001, Nathan Wiger wrote:
> This is very similar to what Params::Validate does right now; in fact,
> the module could well inherit from it.
That'd be tricky since its not OO but you could build on it.
Alternately, I'd be happy to add more features to Params::Validate (I
don't feel
Michael G Schwern wrote:
>
> I think you misunderstand. This isn't named parameters vs prototyped
> parameters vs args as list. The problem is the idea that functions
> should accept *multiple styles by default* which the proposed
> Module::Interface does.
No, it doesn't. Unfortunately, I used
From: Michael G Schwern [mailto:[EMAIL PROTECTED]]
> On Tue, Aug 14, 2001 at 09:55:37AM -0500, Garrett Goebel wrote:
> > > There should be ONE calling style for each sub/method.
> > > Allowing this _will_ cause different people to use different
> > > calling styles and also possible confusion.
>
On Tue, Aug 14, 2001 at 09:55:37AM -0500, Garrett Goebel wrote:
> > There should be ONE calling style for each sub/method.
> > Allowing this _will_ cause different people to use different
> > calling styles and also possible confusion.
>
> It gives us a cleaner way to mix and match order dependa
From: Graham Barr [mailto:[EMAIL PROTECTED]]
> On Mon, Aug 13, 2001 at 04:38:43PM -0700, Nathan Wiger wrote:
> > And allow flexible calling styles. For example, you might say:
> >
> ># import args() for argument validation
> >use Module::Interface qw/args/;
> >
> >sub my_func (@) {
>
On Mon, Aug 13, 2001 at 10:02:29AM -0500, Jarkko Hietaniemi wrote:
> On Mon, Aug 13, 2001 at 09:46:13AM -0500, Garrett Goebel wrote:
> > From: Jarkko Hietaniemi [mailto:[EMAIL PROTECTED]]
> > >
> > > Remember, the goal for Perl 6 is to allow several modules sharing
> > > the same name.
> >
> > D
On Mon, Aug 13, 2001 at 10:45:27AM +0100, Graham Barr wrote:
> On Sat, Aug 11, 2001 at 07:20:11PM -0400, [EMAIL PROTECTED] wrote:
> > On Sat, Aug 11, 2001 at 02:16:49PM -0500, Jarkko Hietaniemi wrote:
> > > One silliness is that the implementation "style" of the module
> > > seems to creep to the
Graham Barr <[EMAIL PROTECTED]> writes:
> > > (1) Foo vs Foo_XS
>
> Why do they need to be named differently ? Only one will be installed.
That is only possible if they have _identical_ APIs.
-- Johan
On Mon, Aug 13, 2001 at 04:38:43PM -0700, Nathan Wiger wrote:
> And allow flexible calling styles. For example, you might say:
>
># import args() for argument validation
>use Module::Interface qw/args/;
>
>sub my_func (@) {
>my %args = args({ positional => [qw/name email phon
Kirrily Robert wrote:
>
> I also think there's too much overhead in learning (and remembering)
> each library's quirks. My most common mistakes when using CPAN or core
> modules occur when the modules have inconsistent interfaces and I forget
> which ones take hashes and which take hashrefs, etc
In perl.perl6.stdlib, you wrote:
>>
>> While we're at it, I think that ExtUtils:: really needs renaming.
>> Nobody talks about "Perl extensions", they talk about modules. Or
>> possibly just about Perl. I actually think the stuff in ExtUtils would
>> be better off in Devel:: with the other deve
On Sat, Aug 11, 2001 at 02:31:47PM -0400, Kirrily Robert wrote:
> Ask wrote:
> >On Thu, 9 Aug 2001, Kirrily Robert wrote:
> >
> >[...]
> >> =head2 The role of CPAN
> >>
> >> Will CPAN's role remain unchanged? Will there be a separate space fo
On Sat, Aug 11, 2001 at 03:51:22PM -0400, Kirrily Robert wrote:
> [ moving to perl6-stdlib only; -meta doesn't need this. ]
>
> Jarkko wrote:
> >> Sys:: should be declared redundant and silly. Sys::Syslog simply
> >> hurts my teeth.
> >
> >Text:: is another silliness, though from for slightly di
On Sat, Aug 11, 2001 at 07:20:11PM -0400, [EMAIL PROTECTED] wrote:
> On Sat, Aug 11, 2001 at 02:16:49PM -0500, Jarkko Hietaniemi wrote:
> > One silliness is that the implementation "style" of the module
> > seems to creep to the naming:
> >
> > (1) Foo vs Foo_XS
>
> Well then, how do you name it
On Mon, Aug 13, 2001 at 09:46:13AM -0500, Garrett Goebel wrote:
> From: Jarkko Hietaniemi [mailto:[EMAIL PROTECTED]]
> >
> > Remember, the goal for Perl 6 is to allow several modules sharing
> > the same name.
>
> Don't you mean several modules sharing a common named interface?
For now, module
From: Jarkko Hietaniemi [mailto:[EMAIL PROTECTED]]
>
> Remember, the goal for Perl 6 is to allow several modules sharing
> the same name.
Don't you mean several modules sharing a common named interface?
Or are you refering to module, version, and author? Or something else?
anything else, you take over maintenance. Your maintenance
consists of moving it into the deprecated branch.
> On the other hand, if Perl 6 modules are going into a perl6/ directory
> or something, that will (eventually) have the effect of deprecating
> everything that's not in ther
their
authors' consent, unless the author is unresponsive to the point where
we can consider the module "abandoned".
On the other hand, if Perl 6 modules are going into a perl6/ directory
or something, that will (eventually) have the effect of deprecating
everything that&
e comments, please follow up to [EMAIL PROTECTED], which is
probably the most suitable place available to us.
K.
=head1 NAME
Perl 6 Modules Plan
=head1 INTRODUCTION
Fundamental premise: almost all Perl 5 modules will be rewritten in Perl 6 at
some point in the future.
When we started writing m
46 matches
Mail list logo
