I felt submitting an RT on
that module, either.
K.
--
Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.net/
There's too much blood in my caffeine system.
e" is useful in some ways and not in others, it seems. The most
useless part of it is the "published modules list", and IMO we should
get rid of the thing.
K.
--
Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.net/
"I've decided to rename [Connect's Melbourne border router] 'Madi's Pants'
because it keeps dropping." -- Madi (from the Netizen quotes file)
he module from there.
Thinking of attacking perlmodlib next, and removing a lot of those long
lists. I'm pretty sure we're better off pointing to web resources for
most of the gunk that's in there.
K.
--
Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.
Hi Ask, perl6-meta, and perl6-stdlib,
Today at YAPC in the Perl 6 session there was some discussion of modules
and what work needs doing in that area for Perl 6.
Basically it breaks down the following two topics:
WHAT goes into the core? (covered by perl6-stdlib)
HOW do we write Perl 6 modules
As many of you may know, I've recently moved to the other side of the
world, and my life's a bit hectic. I hadn't counted on p6-l bursting
into life just now, and while I'd like to keep right up to date with it
I really can't guarantee daily reading.
Would anyone like to volunteer to do weekly s
On Sun, Feb 11, 2001 at 07:13:30PM -0500, Adam Turoff wrote:
> On Sun, Feb 11, 2001 at 05:03:12PM +, Simon Cozens wrote:
> > There's obvious FUD out there and we don't seem to be giving the impression of
> > getting much done, or doing anything to counter it.
>
> Let's be fair. We're not ge
I've got one ready to go on the topic of "Perl 6: the story so far".
I'm presenting it next week at linux.conf.au and would be happy to
submit it for YAPC and/or TPC.
K.
other languages are great. they are a source of features to
steal^Wborrow.
INTERCAL
except maybe intercal
On Tue, Dec 05, 2000 at 11:28:31AM -0800, Nathan Wiger wrote:
>
> Anyways, that's just one suggestion. Do I have any idea where to find
> these mythical people? No, unfortunately. Perhaps some feelers on
> newsgroups might be a good place to start. Personal experience shows
> that this could be a
On Tue, Dec 05, 2000 at 11:05:43AM -0800, Steve Fink wrote:
> David Grove wrote:
>
> > Also, as far as documentation goes, I think it _should_ be written by
> > apprentices, so that non-masters can understand it too. That's always been
> > a huge criticism of the perldocs. That's not grunt work.
This coming Saturday, I'm presenting a paper on Perl 6 (the story so
far) at the Australian Open Source Symposium.
Is anyone interested in looking over my notes and commenting on them
in the next couple of days?
K.
--
Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrop
ld have been like pissing into the
wind.
K.
--
Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.net/
"Darkly hinting of head hitting desk"
-- Megahal (trained on asr), 1998-11-05
east. Regardless of the levels of disapproval,
> generally the disapproval was voiced with at least some courtesy. p5p is
> rather less polite about things.
I, for one, consider this to be a feature, not a bug.
K.
--
Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope
xt
few weeks.
My Netizen email address will continue to function, however I would
prefer most correspondence to be addressed to me at my home address,
[EMAIL PROTECTED]
Thank you in advance for your forbearance,
K.
--
Kirrily "Skud" Robert
[EMAIL PROTECTED]
http://infotrope.net/
Schwern wrote:
> Seperating the men from the boys.
I'll just go get my detachable penis :)
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne V
Mark-Jason Dominus has indicated that he would like to be replaced as
chair of the regex sublist. Would anyone else like to take on this role
for the next few weeks? The responsibilities include:
- weekly report to me
- guide discussion on regex related issues
- encourage RFC authors to redraft
There's been a lot of discussion lately on -meta which implies that the
RFC/brainstorming process has gotten out of control. I personally think
that it's going exactly as it should, and I've seen little to worry
about, which is why I've been fairly hands-off apart from trying to get
some process-
Could we please take discussion of 179 to -data? I think that's where
it should be.
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
Phone: +61 3 9614 0949 Fax: +61 3 9614 0948
> RFC - Prototype RFC Implementations - Seperating the men from the boys.
Feh.
Scuse me while I find my detachable penis.
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
Phone:
Does this discussion pertain to a particular RFC? If so, could the RFC
number please be quoted in the subject?
If it's not already RFC'd, who will volunteer to do it?
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level
Thanks, Ziggy. You rock!
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
Phone: +61 3 9614 0949 Fax: +61 3 9614 0948 Mobile: +61 410 664 994
On Wed, Aug 30, 2000 at 04:43:56PM -0400, Jerrad Pierce wrote:
>Since everyone seems intent on breaking backward compatibility
>(Okay, so no one is explicitly setting out to do so, it is merely often
>dismissed as a non-issue). How about an RFC be done proposing that
>perl6 ship with a module name
(yes, I'm in an RFC-commenting mood today...)
On Wed, Aug 30, 2000 at 02:22:31AM -, Perl6 RFC Librarian wrote:
>Add C keyword to force list context (like C)
Makes sense to me. Does it connect in any way with Damian's generic
want() function?
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> --
On Wed, Aug 30, 2000 at 02:21:19AM -, Perl6 RFC Librarian wrote:
>
>Allow for a list of loop variables in for(each) statements, i.e. & e.g.,
>
> foreach my ($x, $y, $z) (@list) { ... }
Hear, hear. I like this one :)
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
On Wed, Aug 30, 2000 at 04:53:46PM -0400, Bryan C . Warnock wrote:
>On Wed, 30 Aug 2000, Michael Maraist wrote:
>
>> Good idea, but you have it backwards.. If anything, there should be an
>> "explicit" keyword..
>> Remember, we want
>>
>> % perl -p -e 's/foo/bar/g' file.txt
>
>Oh, I know. I thr
On Wed, Aug 30, 2000 at 10:31:48AM -0400, Michael Maraist wrote:
>> Request For New Pragma: Implicit
>
>Good idea, but you have it backwards.. If anything, there should be an
>"explicit" keyword..
This resonates well with me. I had a funny feeling about "use Implicit"
and I wasn't sure what it w
On Wed, Aug 30, 2000 at 02:31:00PM -0600, Nathan Torkington wrote:
>chomp() is best used for chop()s main raison d'etre, removing $/
>from a string. I say we drop chop().
Works for me. Are you going to RFC it?
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source
The most common format I've seen in the field so far is to have "Status:
foo" up with the maintainer and version info, where it's easily seen.
Can we do this instead of a separate section? And can we make it
required, please?
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au
The way people seem to be showing the status of RFCs is by putting
"Status: foo" up near the maintainer info etc. This makes good sense.
Can this be reflected in the sample RFC and the instructions and so on?
K.
- Forwarded message from Peter Scott <[EMAIL PROTECTED]> -
>From: Peter Sc
I've just run a nasty hairy script over the RFC repository and sent
email to those people who I think have language RFCs but haven't put
statuses on them yet.
My aim in this is to figure out which RFCs are still actively under
discussion and which aren't. Some people haven't updated their RFCs
Sumesh,
Please read http://dev.perl.org/ for the correct way to post a Perl 6
RFC. The first thing you need to know is that they should go to
[EMAIL PROTECTED], not direct to the mailing list.
Secondly, you need to make sure that things your'e RFCing aren't already
available in Perl. Some of t
Righto. I'll coach Sumesh through how to post an RFC properly, and how
to check whether something's in Perl yet or not.
DO NOT fill -language with discussions of these pseudo-RFCs. Please.
I'm begging you.
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source dev
On Mon, Aug 21, 2000 at 01:01:20PM -0600, Nathan Torkington wrote:
>Larry Wall writes:
>> I'd entertain a proposal that ... be made a valid term that happens
>> to do nothing, so that you can run your examples through perl -c for
>> syntax checks. Or better, make it an official "stub" for rapid
>
On Fri, Aug 18, 2000 at 08:46:17PM +0100, Richard Proctor wrote:
>
>There is one significant area of perl that has very little attention here
>(other than one of my RFCs) that is regexs.
Are you volunteering to chair a sublist?
*grin*
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://neti
On Sat, Aug 19, 2000 at 05:45:39PM -0700, Peter Scott wrote:
>At first I thought this was a -io item, but then I realized the -io part is
>easy; it's the -language part I need to get right :-)
Um. The -io sublist is called -language-io for a reason -- it's for
language discussions related to IO.
I think all discussion fo RFC 76 (reduce) should be on the new -data
sublist. Jeremy, am I on track here?
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
Phone: +61 3 9614 0949
On Fri, Aug 18, 2000 at 05:22:17PM -0500, David L. Nicol wrote:
>RFC: Perl6 is Final. There will Be No Perl7
>RFC: Everything is Accessible and Mutable
>RFC: The perl6 reference implementation, no matter how slow it is,
>will be written in perl5, in some kind of well defined virtual machine.
>
>>-io = ALL I/O issues, like open/socket/filehandles
>>-subs = ALL sub/method/func issues, like lvalue subs
>>-strict = ALL lexical/global variable scoping issues
>>-objects = ALL OO and module issues
>>-flow = ALL flow/threading issues
>>-errors = ALL er
On Thu, Aug 17, 2000 at 09:19:20AM -0700, Peter Scott wrote:
>
>I realize this is very pedestrian compared to the exception-handling stuff
>we've been tossing around, which could largely be said to render the issue
>moot; but I thought I'd shake the branches anyway and see what fell out.
>
>I'm
This discussion should be on the -datetime sublist. Please do not
discuss this RFC any further on the main language list.
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
Phone:
On Wed, Aug 16, 2000 at 11:15:40PM -0700, Peter Scott wrote:
>
>Sorry I didn't chime in earlier, but I would like to say that I prefer
>published deadlines. Reason: people will talk for as long as you give
>'em. However long a meeting is scheduled for, that's how long it will
>take. We're al
On Wed, Aug 16, 2000 at 10:35:09AM -0700, Nathan Wiger wrote:
>I agree. I think the trend should be to establish some permanent
>sublists, which we're informally leaning towards already. Something
>like:
>
> -io = ALL I/O issues, like open/socket/filehandles
> -subs = ALL sub/method/
On Tue, Aug 15, 2000 at 08:05:25PM -, Perl6 RFC Librarian wrote:
>=head1 TITLE
>
>lvalue subs should receive the rvalue as an argument
>
>=head1 VERSION
>
>Maintainer: Andy Wardley <[EMAIL PROTECTED]>
>Date: 15 Aug 2000
>Version: 1
>Mailing List: [EMAIL PROTECTED]
>Number:
On Wed, Aug 16, 2000 at 12:15:30PM -0500, David L. Nicol wrote:
>
>If "catch" can be defined DURING PARSING
>
>and SYNTAX ERRORS are catchable
>
>error handling can be used to define otherwise
>undefined syntax, becoming a macro language.
Please take this to the -errors sublist. Thanks...
K.
-
(reply-to set to bootstrap)
On Wed, Aug 16, 2000 at 01:36:47AM -0600, Tony Olekshy wrote:
>On this matter, should something like this be a (meta) RFC?
>
> Guidelines for Developing Changes for Perl 6 (v0.1).
There's nothing to stop you writing an RFC on whatever you like :)
However, there's not
OK, weekly report. Ugh.
The language group has generated the vast majority of the 100+ RFCs in
existence, and is suffering under the deluge of 100-200 posts a day. I
would prefer this to be down around 50, but no luck yet :-/ Part of the
problem seems to be timezone related... the lag time bet
Last night we had a Melbourne.pm dinner and we were, of course,
discussing Perl 6 and the language RFCs.
Something that became apparent was that the RFCs are a tad confusing,
and we came up with some things which we thought might help.
Firstly, an RFC should usually only address one point. Some
On Tue, Aug 15, 2000 at 09:27:23PM -0700, Ask Bjoern Hansen wrote:
>LIST: perl6-language-objects
>CHAIR: Nathan Wiger <[EMAIL PROTECTED]>
>MISSION:Develop RFCs related to objects and OO programming in
>Perl, possibly rationalising existing RFCs where they
Please take this discussion to perl6-language-datetime. Thanks!
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
Phone: +61 3 9614 0949 Fax: +61 3 9614 0948 Mobile: +61 410 664
Command line options aren't really a language issue, however I'm not
sure that there is a better list for them. Anyone on bootstrap got any
good ideas?
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins
On Mon, Aug 14, 2000 at 11:27:35PM -, Perl6 RFC Librarian wrote:
>
>Inline Comments for Perl.
What relationship does this have to RFC 5 (multiline comments), and
hasn't the discussion of inline comments occurred in detail already?
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netiz
51 matches
Mail list logo
