Piers Cawley wrote:
[...]
Nope, send it to TPF as discussed. It's what I've said in all the
summaries after all. I just hope that a chunk of it ends up in Larry's
pocket.
Does anyone know if TPF is set up to allow earmarked contributions?
brad
Damien Neil wrote:
On Thu, Dec 05, 2002 at 02:45:39AM -0800, Michael G Schwern wrote:
Explain how having indexes (arrays, substr, etc...) in Perl 6 start at 0
will benefit most users. Do not invoke legacy. [1]
Answer 1: Ignoring legacy, it won't.
Bingo.
Answer 2: Because C uses 0-based i
Flaviu Turean wrote:
[...]
5. if you want to wait for the computing platforms before programming in
p6, then there is quite a wait ahead. how about platforms which will never
catch up? VMS, anyone?
Not to start an OS war thread or anything, but why do people still have
this mistaken impression o
Larry Wall wrote:
[...]
> Maybe we should ... to mean "and so on forever":
>
> @a[0...; 0...:10; 0...:100]
>
> Except then we couldn't use it to mean what Ruby means by it, which
> might be handier in real life.
No more yada-yada-yada?
Brad
Larry Wall wrote:
[...]
> Then Perl language variants could go the other way and be:
>
> PermMicro Perl
> PernNano Perl
> PeroJava Perl
> PerpPython Perl
> PerqQuick Perl
> PerrRuby Perl
> PersStrict Perl
> Pe
The story so far:
On September 13 Jarkko professed a desire for
"a quotish context that would be otherwise like q() but with some minimal extra
typing
I could mark a scalar or an array to be expanded as in qq()." [1]
Seeing this as being especially useful for those of us creating comma
Perl6 RFC Librarian wrote:
[...]
> =head1 TITLE
>
> All perl generated errors should have a unique identifier
>
[...]
> An id string could have some structure associated to enable
> better handling. One suggestion was to follow the lead of VMS.
>
> facility:
> The program
Damian Conway wrote:
>
> Why not just give \I..\E a special "turn-on-interpolation" meaning in
> q{} docs?
>
> $code = '
>
> $x = $y;
> @a = (1..10);
> $name = \I$funcname\E;
>
> # etc.
>
> ';
>
> Damian
Yes. M
Michael G Schwern wrote:
[...]
> Personally, I'd solve this with sprintf():
>
> print F sprintf <<'END', $filename;
> $!
> $! execute a.com, copy and purge
> $!
> $ @sys$login:a.com
> $ copy %s sys$login:*.*
> $ purge sys$login:$filename
> $!
> $ exit
>
> but
Mark-Jason Dominus wrote:
>
> > This reminds me of a related but rather opposite desire I have had
> > more than once: a quotish context that would be otherwise like q() but
> > with some minimal extra typing I could mark a scalar or an array to be
> > expanded as in qq().
>
> I have wanted that
Andy Wardley wrote:
>
> > I know other languages call it zip, but personally I dislike that name
> > as zip() is commonly used with reference to compression. Although
> > I do not have a good alternative.
>
> fold() and unfold()?
>
> merge() and cleave()?
>
> A
collate() and ...?
Perl6 RFC Librarian wrote:
[...]
> This RFC proposes the introduction of a new data type -- the I
[...]
I hereby propose that all current Perl 6 Project Plan deadlines
be extended 3 months so that Damian has more time to come up
with gems like this. I have no idea if it ultimately makes sense
or
"Bryan C. Warnock" wrote:
> On Tue, 08 Aug 2000, Peter Bevan wrote:
[...]
> > Error handling should be supported by it's own keyword
> i.e.: >
> > trap {
> > #CODE
> > }
> > release (error) {
> > # ERROR
> > }
> >
> > (just because I didn't want to steal throw and catch)
>
> Why not? Throw
13 matches
Mail list logo
