On Mon, Sep 26, 2005 at 02:24:33 +0200, Juerd wrote:
> Whenever possible, object should have useful numeric and string
> representations. These are generally lossy, but this is not a problem, because
> a scalar stays a scalar even after being used in a certain context, and the
> object isn't lost.
On Sun, Sep 25, 2005 at 23:21:33 -0700, Ashley Winters wrote:
> On 9/25/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
> > On 9/25/05, Juerd <[EMAIL PROTECTED]> wrote:
> > > We can do better than equivalence testing for colors. Instead, try to
> > > match. Surely a *smart* match operator really is smar
On Sun, Sep 25, 2005 at 23:54:56 -0700, Ashley Winters wrote:
> Localization occurs here. Formatting occurs here.
> Timezone/newline-convention/join-character-specification/whatever
> happens here
This is going too far, IMHO.
What if your app is running in some time zone, generating reports
for
Mark A. Biggar skribis 2005-09-25 19:42 (-0700):
> In a private conversation with Larry this afternoon, he said that by
> default "$foo" and ~$foo and $foo.as(Str) all give the same result
> (assuming scalar context, etc.). And that "@foo[]" and [EMAIL PROTECTED] and
> @foo.as(Str) are the same
On 26/09/05, Yuval Kogman <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 25, 2005 at 23:54:56 -0700, Ashley Winters wrote:
> > Localization occurs here. Formatting occurs here.
> > Timezone/newline-convention/join-character-specification/whatever
> > happens here
>
> This is going too far, IMHO.
I can't
I thought we'd switched to a Monday deadline for the summary and a Sunday night
roll over. I just noticed your last summary ended on a Monday night.
--
Piers Cawley <[EMAIL PROTECTED]>
http://www.bofh.org.uk/
On 9/26/05, Yuval Kogman <[EMAIL PROTECTED]> wrote:
> I think that this role should define the dump operator. Perhaps
> prefix or postfix ?! can work... That seems fairly obvious. For
> example
>
> warn "Done fetching $url, { $ua?! }";
>
> Let's call it the wtf operator.
No, please... how
HaloO,
Juerd wrote:
wolverian skribis 2005-09-24 13:45 (+0300):
Why not define .chars like this:
Context Return value
itemamount of units
listunits themselves
I still have my objections to this outside-in flow of type
information.
Originally I thought that .el
Hi,
please configure your e-mail client to use "> " (greater-than, space)
for quoting, if possible. It currently uses ">" (greater-than).
TSa skribis 2005-09-26 13:43 (+0200):
> >>Why not define .chars like this:
> >> Context Return value
> >> itemamount of units
> >> list
Michele Dondi <[EMAIL PROTECTED]> writes:
> Every time I've desired a feature for Perl6 it has turned out that either it
> was already planned to be there or I have been given good resons why it would
> have been better not be there.
And you've done it again. What you ask for is already there. Se
We've had several discussions of .chars and .elems, and I said
something about objects in certain contexts.
In the discussion about objects, I left item and list context out,
because in those contexts, always the object is just itself.
One thing makes .chars and .elems look symmetric: they are bo
Piers Cawley skribis 2005-09-26 16:34 (+0100):
> And you've done it again. What you ask for is already there. See below.
> next if (($_ ne 'boo')..undef)
> if 0..MAX { push @buffer, $_; next }
IIRC, flip flop will not return as the ".." operator. Also, the global
state of syntactic flip f
On Mon, Sep 26, 2005 at 05:42:31PM +0200, Juerd wrote:
: Piers Cawley skribis 2005-09-26 16:34 (+0100):
: > And you've done it again. What you ask for is already there. See below.
: > next if (($_ ne 'boo')..undef)
: > if 0..MAX { push @buffer, $_; next }
:
: IIRC, flip flop will not retu
Luke Palmer <[EMAIL PROTECTED]> writes:
> On 9/25/05, Yuval Kogman <[EMAIL PROTECTED]> wrote:
>> I propose a new model - each exception has a continuation that
>> allows it to be unfatalized.
>
> I think we've already talked about something like this. But in the
> presence of "use fatal", it make
The Perl 6 Summary for the week ending 2005-09-25
Hello all. It's another Monday afternoon, which means I'm writing
another summary. There's no cricket to distract me this week, so I'm
letting iTunes Party Shuffle attempt to distract me instead.
This week in perl6-compiler
Nobody s
HaloO,
Juerd wrote:
Can you explain please what "outside-in" means to you?
TSa wrote:
BTW, does everybody expect more than one prefix numerifyer beeing
redundant or is there an idea of (+ (+ @foo)) beeing modelled
Juerd answered:
It's providing context to something that was already providi
HaloO,
Larry Wall wrote:
... though we haven't decided what to call the flipflop operator.
Sorry, I'm totally out of scope to what 'the flipflop operator' is.
Could you be so kind to give some hints. Thanks in advance.
if state $s ?? $s = falsify() !! $s = truify() && !falsify() {...}
TSa skribis 2005-09-26 19:39 (+0200):
> Sorry, I'm totally out of scope to what 'the flipflop operator' is.
> Could you be so kind to give some hints. Thanks in advance.
http://perldoc.perl.org/perlop.html#Range-Operators
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl
HaloO,
Piers Cawley wrote:
Exactly which exception is continued?
The bottommost one. If you want to return to somewhere up its call chain, do:
$!.caller(n).continue(42)
Whow, how does a higher level exception catcher *in general* know
what type it should return and how to construct it. The
HaloO,
Juerd wrote:
TSa skribis 2005-09-26 19:39 (+0200):
Sorry, I'm totally out of scope to what 'the flipflop operator' is.
Could you be so kind to give some hints. Thanks in advance.
http://perldoc.perl.org/perlop.html#Range-Operators
Thanks. I'm glad that 1..Inf these days is just a l
TSa skribis 2005-09-26 20:32 (+0200):
> Does someone consider this 'inner boolean state' and the 'magical
> auto-increment algorithm if the operands are strings' of the Perl5
> range op a feature worth preserving?
Yes, many someones do.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http:/
HaloO,
Yuval Kogman wrote:
if greenish describes the color
Indeed, it sounds like Yoda Speak: "If greenish that color is,
modifying it I will." Same in the German version. I don't know
of hebrew though.
demonstrates the lack of transitivity in matching...
Sorry, but don't you mean
Think about adding \& to the replacement part of a s///.
As in sed, the & means the whole match.
Then one can do
s/$search/*\&*/go
in stead of
s/($search)/*\1*/go
and there needs to be no $1 variable set up.
(I assume that using () always makes a $1 available, even if it is not
being us
Ruud H.G. van Tol skribis 2005-09-26 21:27 (+0200):
> Think about adding \& to the replacement part of a s///.
> As in sed, the & means the whole match.
Do you know Perl 5's $& variable? What you want isn't exactly new for
Perl.
In Perl 6, the match object $/ will instead be used. It's a bit hard
Juerd:
> Ruud H.G. van Tol:
>> Think about adding \& to the replacement part of a s///.
>> As in sed, the & means the whole match.
>
> Do you know Perl 5's $& variable? What you want isn't exactly new for
> Perl.
Yes I certainly know it. That it slows things down too.
A point was to not set up a
On Sep 26, 2005, at 4:19 PM, Juerd wrote:
Perl 5's $& is inefficient because of this. If the variable is used
anywhere, Perl will for every regex used capture everything.
My understanding is that this died with 5.10. Is that right?
--Dks
On Mon, Sep 26, 2005 at 05:00:00PM -0400, David Storrs wrote:
>
> On Sep 26, 2005, at 4:19 PM, Juerd wrote:
> >Perl 5's $& is inefficient because of this. If the variable is used
> >anywhere, Perl will for every regex used capture everything.
>
> My understanding is that this died with 5.10. Is
TSa <[EMAIL PROTECTED]> writes:
> HaloO,
>
> Piers Cawley wrote:
>>>Exactly which exception is continued?
>> The bottommost one. If you want to return to somewhere up its call chain, do:
>> $!.caller(n).continue(42)
>
> Whow, how does a higher level exception catcher *in general* know
> what typ
On Mon, Sep 26, 2005 at 17:40:52 +0100, Piers Cawley wrote:
> Luke Palmer <[EMAIL PROTECTED]> writes:
>
> > On 9/25/05, Yuval Kogman <[EMAIL PROTECTED]> wrote:
> >> I propose a new model - each exception has a continuation that
> >> allows it to be unfatalized.
> >
> > I think we've already talked
On Mon, Sep 26, 2005 at 21:02:06 +0200, TSa wrote:
> >demonstrates the lack of transitivity in matching...
>
> Sorry, but don't you mean commutativity? Transitivity of relations
> requires applying it twice to three values and then concluding it
> applies to the unchecked combination as well:
Ye
On Mon, Sep 26, 2005 at 18:12:23 +0100, The Perl 6 Summarizer wrote:
> Allomopherencing
> Not satisfied with inventing Exceptuations, Yuval invented
> Allomopherencing as well. Just don't ask me what it means because I
> don't know.
It was just a bad joke on Exceptuation's expense ;-
On Sun, Sep 25, 2005 at 08:29:07PM +0300, Yuval Kogman wrote:
: Is there any situation where a compile time error is not a good
: thing to have?
Sure, when it slows down your compiler so much that it's useless for
running code that doesn't have the error, especially if it's a rare
error that is li
On Mon, Sep 26, 2005 at 17:36:04 -0700, Larry Wall wrote:
> Sure, when it slows down your compiler so much that it's useless for
> running code that doesn't have the error, especially if it's a rare
> error that is likely to be caught some other way anyway. Where to
> balance this should be the de
33 matches
Mail list logo
