Simon Cozens wrote:
[...]
> I'm just not sure it's fair on Old World hackers. Will there be a way to stop
> Perl upgrading stuff to Unicode on the way in?
and I'm probably not the only Old World hacker that would
prefer a build option to simply eliminate Unicode support altogether...
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
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
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:
On Mon, Dec 02, 2002 at 04:42:52PM -0500, Joseph F. Ryan wrote:
[...]
: As far as I know, *nothing* is special in a single quoted heredoc.
Here docs is where you *most* want the \qq[] ability. It is assumed that
the sequence "\qq[" will not occur by accident very often in the
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
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
Nathan Wiger wrote:
[...]
> RFC 164 v2 has a new syntax that lets you do the above or, if you want:
>
>$this = s/foo/bar/, $that;
>@these = s/foo/bar/, @those;
>
> Consistent with split, join, splice, etc, etc.
I often use the comma operator like this
s/foo/bar/, $n++ if $x;
If "s"
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
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
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
11 matches
Mail list logo
