On Tue, Jun 04, 2002 at 04:15:02PM -0400, John Siracusa wrote in
response to me:
> > Frankly, I'd argue that nothing in 6PAN ought to be in alpha/beta state.
> . . .
> Nah, I think it's useful to be able to upload "unstable" versions to 6PAN to
> get the widest possible audience of testers. It'
On Tue, Jun 04, 2002 at 01:11:58PM -0700, David Wheeler wrote:
> On 6/4/02 12:59 PM, "Steve Simmons" <[EMAIL PROTECTED]> claimed:
>
> > Actually, for 6PAN I think they should have to pass. And maybe we
> > need a bug submission setup, and status checks, a
On Tue, Jun 04, 2002 at 12:59:38PM -0400, John Siracusa wrote:
> In the spirit of Simon's desire to see "radical changes" when appropriate, I
> propose the following high-level goals for 6PAN . . .
> 1. Multiple versions of the same module may be installed on a single system
> with no possibilit
On Tue, Jun 04, 2002 at 05:40:08PM +0100, Simon Cozens wrote:
> Steve Simmons:
> > We have said that perl5 will be *mostly* mechanically translatable into
> > perl6.
> And we shall keep saying this until we believe that it is true?
*grin*
My apologies for using the wrong
On Tue, Jun 04, 2002 at 04:13:36PM +0100, Simon Cozens wrote:
Hmm, June 4. Independence day, with an off by 1 error. Must be a C
program involved somewhere. :-)
In brief, I'm with Damien on this one. IMHO C++ is an ugly bastard of
a programming language because they cut the cord ineffective
On Sun, Jan 13, 2002 at 12:55:26AM -0800, Brent Dax wrote:
>
> It's meant to be a simple fallback for languages that are too pathetic
> to implement their own regex compiler. ("FooLang should have regular
> expressions, but I'm too lazy! I'll just use rx_compile!") Currently
> I'm thinking of
> Perl6 should ship with a simple utility that shows all modules a program
> uses, and all modules those modules use.
Presumably with the caveat that no usage list can be generated for any
missing modules.
Many thanks to all for the pointers.
Paul Johnson wrote:
> I don't think any proposal of this nature would be conplete without a
> consideration of these aspects.
Agreed.
Paul Johnson wrote:
> Has anyone considered the problems associated with XS code, or whatever
> its replacement is?
Pardon my ignorance, but what's XS code?
On Fri, Jan 26, 2001 at 02:08:01PM -0600, Garrett Goebel wrote:
> Discussion of RFC 271 and 194 on pre and post handlers for subroutines
> reminded me of Larry's desire for Perl 6 to support the coexistence of
> different versions of modules.
>
> Besides http://dev.perl.org/rfc/78.pod, are there
On Mon, Aug 28, 2000 at 04:10:01PM -0400, Eric Roode wrote:
> Peter Scott wrote:
> >Graham Barr once allowed as how he thought it would be neat if you could say
> >
> > for my($x, $y, $z) (@list) { ... }
I too am pushing for this feature, to the point where I'm considering
an rfc on the topic
On Tue, Aug 29, 2000 at 09:15:35AM +0100, John McNamara wrote:
> At 13:11 28/08/00 -0400, Steve Simmons wrote:
> >To tell the truth, this third item should probably should become
> >a separate RFC, and if you'd like to simply say one is forthcoming,
> >that'd be
General comment on all the discussion of HERE docs.
When HERE docs cause you a problem, don't use 'em. There is little win
if any over
print << HERE;
Dear Sir:
You owe me bucks. Pay up.
Me.
HERE
and
$msg =
'Dear Sir:
You owe
On Thu, Aug 24, 2000 at 03:40:00PM -, Perl6 RFC Librarian wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Case ignoring eq and cmp operators
IMHO this problem is better solved by using =~ and its brethren,
which already allow you to
I'd like to see eq and it's brethen retained, as dammit there are times
I want to know (-w) if numbers are turning up when there should be
words and vice-versa. However, spinning off of something Randal wrote:
> Yes, but what about:
>
> $a = '3.14'; # from reading a file
> $b =
On Thu, Aug 17, 2000 at 08:46:53PM -, Perl6 RFC Librarian wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Implicit counter in for statements, possibly $#.
Having read over the entire discussion, I want to make a few comments
and thr
On Wed, Aug 16, 2000 at 08:03:31PM -, Perl6 RFC Librarian wrote:
> Perl should provide a mechanism to have common code autoloaded from a
> file. . . .
> A C file could be used to set system-wide defaults that
> the system administrator would like to promote. For instance,
> C could turn on
On Wed, Aug 16, 2000 at 02:38:33PM -0400, Uri Guttman wrote:
> i see problems with overlapping areas. I/O callbacks fall under both io
> and flow IMO. some of the error handling like dying deep in eval and
> $SIG{DIE} also fall under error and flow.
This is true, and inevitable. But IMHO it'd b
This discussion would be a better fit in [EMAIL PROTECTED]
My philosophy - do nothing unless its needed. Therefore there are no
rules, and I'll attempt to avoid creating any. I remain subscribed
to language-flow, and will redirect appropriate discussion to here.
Our deadline - August 29. It's actually a little tighter than that,
because on the morning
On Sun, Aug 13, 2000 at 07:35:06PM -0700, Peter Scott wrote:
> At 03:30 PM 8/13/00 -0500, David L. Nicol wrote:
> >Whose RFC deals with this?
> 63, 70, 80, 88 and 96. There would appear to be a groundswell of interest :-)
Well yes, but they represent three authors with (as best I can tell)
pr
21 matches
Mail list logo
