Mark Stosberg wrote:
> The formal definition of "Inf" appears to be missing from the spec
> documents. Since I'm not exactly sure how Perl 6 treats "Inf", I'll
> leave submitting this patch to someone else.
>
> Once the spec is added, a smart link to it should be added from:
> t/builtins/math/infi
Mark Stosberg wrote:
> The formal definition of "Inf" appears to be missing from the spec
> documents. Since I'm not exactly sure how Perl 6 treats "Inf", I'll
> leave submitting this patch to someone else.
>
> Once the spec is added, a smart link to it should be added from:
> t/builtins/math/infi
Steve (>):
"If you declare a lexical twice in the same scope, it is the same lexical"
I would argue for: If you declare a lexical twice in the same scope, it is an
error!
I agree.
Enforcing one and only one declaration feels like a Good Thing, for
Juerd's reasons. With me, multiple 'my' for
On Mon, Sep 11, 2006 at 11:12:00AM -0700, Larry Wall wrote:
: On Mon, Sep 04, 2006 at 08:54:02PM +0200, TSa wrote:
: : But are assignment ops allowed as initializer?
: :
: : my $z = $p but= { .y = 17 };
:
: Why not? It's only the first = that's potentially special. (And it's
: only for non-my
On Mon, Sep 04, 2006 at 08:54:02PM +0200, TSa wrote:
: But are assignment ops allowed as initializer?
:
: my $z = $p but= { .y = 17 };
Why not? It's only the first = that's potentially special. (And it's
only for non-my, since my's = is an ordinary assignment at normal
run time.) I don't see
On Mon, Sep 11, 2006 at 09:18:19AM -0700, Larry Wall wrote:
: .PKG -> .WHAT
I should have said
.ref-> .WHAT
there, since it was the intention to rename .ref that brought all this
on in the first place. (And what you actually get from .WHAT is the
prototype object
On Mon, Sep 11, 2006 at 11:58:28AM +0800, Audrey Tang wrote:
: Consider these cases:
: [=] $x, $y, $z;
: [+=] $a, $b, $c;
:
: S03 is currently inconsistent. It first says these are not supported:
:
: The final metaoperator in Perl 6 is the reduction operator. Any
: infix operator (excep
On Mon, Sep 11, 2006 at 10:59:20AM -0600, David Green wrote:
: In that case, .WHO definitely makes more sense for the name.
I don't see it. Who I am is my identity. What I am is a Person or some such.
Larry
On 9/11/06, Larry Wall wrote:
Only that I'm thinking of renaming all the meta-ish methods to use
interrogative pronouns:
.META-> .HOW
.SKID-> .WHO
.PKG -> .WHAT
.VAR -> .WHERE
.WHO and .WHAT strike me as better being swapped. Maybe...
or some such. Not s
Steve Lukas skribis 2006-09-11 4:35 (-0700):
> "If you declare a lexical twice in the same scope, it is the same lexical"
> I would argue for: If you declare a lexical twice in the same scope,
> it is an error!
I agree.
The reason that I love "my $foo" is that it always gives me a new
variable.
On Mon, Sep 11, 2006 at 08:59:51AM -0700, David Brunton wrote:
: Hi all,
:
: There is currently a mismatch between S12 and Pugs. The former specifies
$obj.META, the latter has implemented $obj.meta.
.META is more correct at the moment.
: Is there any reason I shouldn't change the tests from me
Hi all,
There is currently a mismatch between S12 and Pugs. The former specifies
$obj.META, the latter has implemented $obj.meta.
Is there any reason I shouldn't change the tests from meta to META, make the
corresponding changes in Pugs.Prim, and then fix any other examples or modules
it brok
On Mon, Sep 04, 2006 at 10:52:35PM -0700, Trey Harris wrote:
: In a message dated Tue, 5 Sep 2006, Ph. Marek writes:
: >I now had a look at http://dev.perl.org/perl6/doc/design/syn/S06.html
: >but didn't find what I meant. Sorry if I'm just dumb and don't
: >understand you (or S06); I'll try to e
On Mon, Sep 11, 2006 at 04:35:08AM -0700, Steve Lukas wrote:
>
> I would argue for: If you declare a lexical twice in the same scope, it is an
> error!
>
> Well, this error happens most likely due to my tiredness and I want the
> compiler to wake me up.
> This can be important because I would
Hello,
perhaps I've missed a discussion about it, but I can't find a reason for a
(IMHO infelicitous) specification. In S04 is said:
"If you declare a lexical twice in the same scope, it is the same lexical"
I would argue for: If you declare a lexical twice in the same scope, it is an
error!
15 matches
Mail list logo