Nathan Torkington <[EMAIL PROTECTED]> writes:
> Tom Christiansen writes:
> > What is the purpose of ghettoizing everying cohering topic? Making
> > us subscribe to infinite lists to wear us down?
>
> Yes.
>
> If you really care about the topic, you'll join the list. If you
> don't care, stay
> From: John Porter [mailto:[EMAIL PROTECTED]]>
> > ..at least if new newsgroups appear, you get notified about it!
>
> Speaking of which, I believe the plan was to announce new list
> creations on perl6-announce; can someone confirm that this is
> actually happening?
I'm getting them.
> ..at least if new newsgroups appear, you get notified about it!
Speaking of which, I believe the plan was to announce new list
creations on perl6-announce; can someone confirm that this is
actually happening?
--
John Porter
On Wed, Aug 02, 2000 at 08:27:19PM -0600, Tom Christiansen wrote:
> What you're doing here is recreating USENET. But badly . . .
> Is there an open NNTP server running with all these as the perl.*
> groups? That would help a lot.
Please, please, please. I'm already considering moving these
s
On Thu, Aug 03, 2000 at 12:51:10PM +1000, [EMAIL PROTECTED] wrote:
> Programer Modifiable Warnings and Error Messages
> Brust, Corwin" <[EMAIL PROTECTED]>
. . .
> Removing/fixing $[line noise here] variables
> Corwin Brust <[EMAIL PROTECTED]>
That second is actually mine. Ba
t;
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, August 02, 2000 10:18 PM
Subject: Re: RFC stuff
> On Wed, Aug 02, 2000 at 08:13:08PM -0600, Tom Christiansen wrote:
> > >> Making us subscribe to infinite lists to wear us down?
> > >You know about perl6-all, right?
> > No
On Wed, 2 Aug 2000, Jonathan Scott Duff wrote:
> On Wed, Aug 02, 2000 at 07:34:36PM -0700, Nathan Wiger wrote:
> > > Deprecate localtime() and replace with
> >
> > I'm willing to take a first whack at this one (but only with lots of
> > input from others).
>
> I'll help. Let's call the re
On Wed, Aug 02, 2000 at 07:34:36PM -0700, Nathan Wiger wrote:
> > Deprecate localtime() and replace with
>
> I'm willing to take a first whack at this one (but only with lots of
> input from others).
I'll help. Let's call the replacement gmt2date() for now.
gmt2date() should at least (IMH
> "TC" == Tom Christiansen <[EMAIL PROTECTED]> writes:
>> I've just asked for a multiline comment sublist to be set up. Do any
>> of the rest of these RFCs want/need a sublist?
TC> What is the purpose of ghettoizing everying cohering topic? Making
TC> us subscribe to infinite list
>Russ talked about doing that. I think it would have to be called
>nntp.perl.org.
I can trivially repoint the old news.perl.com to wherever works best.
--tom
On Thu, 3 Aug 2000, Simon Cozens wrote:
> > Is there an open NNTP server running with all these as the perl.*
> > groups? That would help a lot.
>
> It would, yes. I've been toying with the idea of setting one up, but
> I think it should be news.perl.org
Russ talked about doing that. I think i
OK, I'm now up to date on perl6-language. Ugh.
Here's the RFC list as it currently stands. I'll keep reposting this
every few days as it changes. I'll also put it up at:
http://infotrope.net/opensource/software/perl6/
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
At 10:27 PM 8/2/00, Tom Christiansen wrote:
> >What extra could reasonably have been done?
>
>Should one really have to find the the time to read each of *hundreds*
>of messages each and every day in order to keep up with this stuff?
>Or should one be held accountable to for eyes glazing over admi
On Wed, Aug 02, 2000 at 08:11:36PM -0600, Tom Christiansen wrote:
>
>That seems like a *really* bad idea, since anyone who misses the
>creation doesn't get to play, nor does someone who changes their
>mind later. Well, not easily.
>
>That every topic should have its own list is a pain in the ass.
On Wed, Aug 02, 2000 at 07:34:36PM -0700, Nathan Wiger wrote:
> > That Perl should stay Perl
>
> Do we need an RFC for this? Seems like this is more of a "guiding
> concept" that should be intergrated into everything. Just my opinion.
Then we need to enshrine it. I'll cook something up soon.
--
> Reimplement Warnings and Tainting as Pragmas
> Nathan Wiger <[EMAIL PROTECTED]>
You can delete this one. 'use warnings' is already in 5.6 (sorry!) and
tainting looks near-impossible (thanks Larry for the insight!). I might
(after tons of research) resubmit something on tainting, but for
On Wed, Aug 02, 2000 at 08:27:19PM -0600, Tom Christiansen wrote:
> Should one really have to find the the time to read each of *hundreds*
> of messages each and every day in order to keep up with this stuff?
Nope. That's why you can select which lists you want to join.
I think you're trying to h
>What extra could reasonably have been done?
Should one really have to find the the time to read each of *hundreds*
of messages each and every day in order to keep up with this stuff?
Or should one be held accountable to for eyes glazing over adminstrative
metadiscussions (a crack into which for
On Wed, 2 Aug 2000, Tom Christiansen wrote:
> >Tom Christiansen writes:
> >> What is the purpose of ghettoizing everying cohering topic? Making
> >> us subscribe to infinite lists to wear us down?
>
> >Yes.
>
> >If you really care about the topic, you'll join the list. If you
> >don't care, s
On Wed, Aug 02, 2000 at 08:13:08PM -0600, Tom Christiansen wrote:
> >> Making us subscribe to infinite lists to wear us down?
> >You know about perl6-all, right?
> Nope, I didn't.
> Which is the very problem of which I was speaking.
> Secret cabals and all.
It was publicly announced, although the
On Wed, Aug 02, 2000 at 08:13:08PM -0600, Tom Christiansen wrote:
> >> Making us subscribe to infinite lists to wear us down?
> >You know about perl6-all, right?
>
> Which is the very problem of which I was speaking.
> Secret cabals and all.
So secret it was recorded on:
i) The perl6 metalis
>> Making us subscribe to infinite lists to wear us down?
>You know about perl6-all, right?
Nope, I didn't.
Which is the very problem of which I was speaking.
Secret cabals and all.
--tom
Tom Christiansen writes:
> That seems like a *really* bad idea, since anyone who misses the
> creation doesn't get to play, nor does someone who changes their
> mind later. Well, not easily.
>
> That every topic should have its own list is a pain in the ass.
It's an experiment. Time will tell
>Tom Christiansen writes:
>> What is the purpose of ghettoizing everying cohering topic? Making
>> us subscribe to infinite lists to wear us down?
>Yes.
>If you really care about the topic, you'll join the list. If you
>don't care, stay off the list and don't bother the happy workers.
>That's
On Wed, Aug 02, 2000 at 08:05:15PM -0600, Tom Christiansen wrote:
> >I've just asked for a multiline comment sublist to be set up. Do any
> >of the rest of these RFCs want/need a sublist?
>
> What is the purpose of ghettoizing everying cohering topic?
To get those people who actually care a
Tom Christiansen writes:
> What is the purpose of ghettoizing everying cohering topic? Making
> us subscribe to infinite lists to wear us down?
Yes.
If you really care about the topic, you'll join the list. If you
don't care, stay off the list and don't bother the happy workers.
That's the pla
>I've just asked for a multiline comment sublist to be set up. Do any
>of the rest of these RFCs want/need a sublist?
What is the purpose of ghettoizing everying cohering topic? Making
us subscribe to infinite lists to wear us down?
--tom
> Formats out of core
> Switch statement
>
> Anyone want to put their name next to them?
Me.
Damian
Here are the language RFCs I'm aware of:
Multiline comments
Michael J. Mathews <[EMAIL PROTECTED]>
Lexical scoping by default
J. David Blackstone <[EMAIL PROTECTED]>
Higher resolution time valuse
Gisle Aas <[EMAIL PROTECTED]>
AUTOLOAD declining
Leon Brocard <[EMAI
29 matches
Mail list logo
