on
that module, either.
K.
--
Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.net/
There's too much blood in my caffeine system.
,
why burden new authors with it?
I raised this on [EMAIL PROTECTED] the other day in fact. Register
namespace 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
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.net/
Fist it. It's my solution to everything
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
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 getting
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
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.
mstevens other languages are great. they are a source of features to
steal^Wborrow.
Skud INTERCAL
mstevens except maybe intercal
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. That's
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
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://infotrope.net/
Today
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.net/
"Darkly hinting of head hitting desk"
-- Megahal (trained on asr), 1998-11-05
e
wind.
K.
--
Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.net/
"Darkly hinting of head hitting desk"
-- Megahal (trained on asr), 1998-11-05
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 VIC
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:
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
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
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
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/
Open
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
(yes, I'm in an RFC-commenting mood today...)
On Wed, Aug 30, 2000 at 02:22:31AM -, Perl6 RFC Librarian wrote:
Add Clist keyword to force list context (like Cscalar)
Makes sense to me. Does it connect in any way with Damian's generic
want() function?
K.
--
Kirrily Robert -- [EMAIL
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 named
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 threw it in
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/
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
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
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
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 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.
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
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.
--
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: 107
I think
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/func
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
34 matches
Mail list logo
