# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131838]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131838 >
14:16 Zoffix m: "{$:x}"
14:16 camelia rakudo-moar 5d200f: OUTPUT: «5===SORRY!
S15-unicode.pod
Log Message:
---
Update S15 so as not to include references to a uniprops hash.
It had been changed in some places but not others.
Commit: 556410aa33fbae27308928a0d97f9ba6ddc3b699
https://github.com/perl6/specs/commit/556410aa33fbae27308928a0d97f9ba6ddc3b699
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #128646]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128646 >
m: say 2.Rat.polymod: 0
rakudo-moar 980f49: OUTPUT«Attempt to divide 2 by zero using pol
On 2016-01-14 06:39, ToddAndMargo wrote:
I was on the IRC a few days back. I am a little bit unsure of
what and how to use it. Seems like a bunch of one line questions
and answers.
It is. but the turn-around time is very low and the reply quality is
very high. Also, you'll use nopaste for
2016 05:54 PM, Brent Laabs wrote:
Nothing is Forbidden! Everything is Permissible!
Also it would make it hard to talk about "is repr('CPointer')" and the
Pointer type in NativeCall.
While underneath the hood Scalar containers have pointers to values,
it's not a particularly
x27;s more useful to use an OO or
FP perspective. Where in Perl 5 you'd have array references and such, in
Perl 6 can use an Array both as a reference and its values.
But if you'd like to introspect what variables are actually doing, we have
things like $foo.VAR to let you do that too. O
Hi All,
Just out of curiosity, is the word "Pointer" a "forbidden" word
in Perl 6 correspondences? Will using the two together "Reference
Pointer" get me in hot water?
-T
--
~~
Computers are like air conditioners.
They malfunction when you open windows
:
M S02-bits.pod
Log Message:
---
Mention handling circular references in .perl
M S17-concurrency.pod
>
> Log Message:
> ---
> [S17]: Add references to hyperops, feeds, and junctions.
>
>
>
-concurrency.pod
Log Message:
---
[S17]: Add references to hyperops, feeds, and junctions.
-functions.pod
Log Message:
---
[S29] updated references to S32 synopsis
On Fri, 30 Jul 2010 19:06:09 +0200
Leon Timmermans wrote:
> On Fri, Jul 30, 2010 at 6:21 PM,
> R. Dresens wrote:
> > is still an 'Array()'. So I'm really confused about the
> > intricate difference between...
> >
> > my $x = [1, 2, 3]
> >
> > ...and...
> >
> > my @y = (1, 2, 3); my $x = \
On Fri, Jul 30, 2010 at 6:21 PM, R. Dresens wrote:
> Yes, but aren't captures somehow replacements for references in
> general... and therefore also array references? The reason why I
> assume that is that I (wrongly?) expected a "real" 'Array()' when I
> used
On Fri, 30 Jul 2010 14:31:31 +0200
Leon Timmermans wrote:
> On Thu, Jul 29, 2010 at 8:30 PM, R. Dresens wrote:
>
> > And what about this?...
> > my $x = [3, 4]; my @y = 1, 2, |$x, 5, 6; say @y.perl;
> I think that you meant to do is this:
>
> my $x = [3, 4]; my @y = 1, 2, @($x), 5, 6;
On Thu, 29 Jul 2010 20:55:39 -0700
Darren Duncan wrote:
> R. Dresens wrote:
> > I have some issues with the behavior related to array references
> > and their actual replacements known as "captures" (as far as I'm
> > correct).
> Captures are not replace
On Thu, Jul 29, 2010 at 8:30 PM, R. Dresens wrote:
> And what about this?...
>
> my $x = [3, 4]; my @y = 1, 2, |$x, 5, 6; say @y.perl;
>
> ...I actually expected `[1, 2, 3, 4, 5, 6]`, since I was under the
> impression that the '|' was some kind of "flatten" or
> "interpolation" operator.
>
>
R. Dresens wrote:
I have some issues with the behavior related to array references and
their actual replacements known as "captures" (as far as I'm correct).
Captures are not replacements for Arrays in general; they serve different
purposes.
Use an Array when you want t
Hello,
I've been experimenting with Perl 6 for quite a while, and so now and
then I upgrade my Rakudo installation. Today, I upgraded to Rakudo
star.
I have some issues with the behavior related to array references and
their actual replacements known as "captures" (as far
On Mon, Feb 01, 2010 at 06:12:16PM -0800, Jon Lang wrote:
: Larry Wall wrote:
: > But also note that there are several other ways to predeclare
: > types implicitly. The 'use', 'require', and 'need' declarations
: > all introduce a module name that is assumed to be a type name.
:
: Just to clarif
Larry Wall wrote:
> But also note that there are several other ways to predeclare
> types implicitly. The 'use', 'require', and 'need' declarations
> all introduce a module name that is assumed to be a type name.
Just to clarify: it's possible to define a module within a file,
rather than as a fi
On Tue, Feb 02, 2010 at 12:23:50AM +0100, Carl Mäsak wrote:
: Another thing I started thinking about: if Perl 6 professes to be able
: to put on the hat -- syntactically and semantically -- of most any
: other programming language out there, through the use of a simple 'use
: Language::Java' or 'us
Larry (>):
> [Long exposition on the philosophy of predeclaration]
>
> Hope this helps, or I just wasted a lot of time. :-)
It did help. Thanks.
A comment on one part, though:
> But I also think that type recursion is likelier to indicate a design
> error than function recursion [...]
I do too
o occur at all (as long as none of the features needed
: > from B are ever needed).
:
: And just to finish it off... are you allowed to do 'class B { ... }'
: even after "declaring the real B"?
STD does not currently allow it because you have to install the name
immediately
On Mon, Feb 1, 2010 at 3:46 PM, Patrick R. Michaud wrote:
> On Mon, Feb 01, 2010 at 05:55:47PM +0100, Carl Mäsak wrote:
>> Is it allowed to do 'class B { ... }' several times in different files
>> before finally declaring the real B? If so, then I'd consider it
>> equivalent to my proposed keyword
On Mon, Feb 01, 2010 at 05:56:09PM +0100, Jan Ingvoldstad wrote:
> On Mon, Feb 1, 2010 at 17:46, Patrick R. Michaud wrote:
> > There's a third way:
> >
> >class B { ... }# introduce B as a class name without definition
> > class A { sub foo { B::bar } }
> >
> >class B { sub bar { A
On Mon, Feb 01, 2010 at 05:55:47PM +0100, Carl Mäsak wrote:
> Is it allowed to do 'class B { ... }' several times in different files
> before finally declaring the real B? If so, then I'd consider it
> equivalent to my proposed keyword, and thus there'd be no need for the
> latter.
Yes. And "decl
On Mon, Feb 01, 2010 at 10:10:11AM -0800, yary wrote:
: A slight digression on a point of fact-
:
: On Mon, Feb 1, 2010 at 9:32 AM, Larry Wall wrote:
: ...
: > You are correct that the one-pass parsing is non-negotiable; this is
: > how humans think, even when dealing with unknown names.
:
: It'
A slight digression on a point of fact-
On Mon, Feb 1, 2010 at 9:32 AM, Larry Wall wrote:
...
> You are correct that the one-pass parsing is non-negotiable; this is
> how humans think, even when dealing with unknown names.
It's common for people to read a passage twice when encountering
somethin
On Mon, Feb 1, 2010 at 9:32 AM, Larry Wall wrote:
> But I also think that type recursion is likelier to indicate a design
> error than function recursion, so I'm not sure how far down this road
> we want to go. We could, for instance, create a new type name every
I was going to say "I use self-r
Please don't assume that rakudo's idiosyncracies and design fossils
are canonical. STD does better namespace management in some respects,
particularly in accepting the approved predeclaration form:
class Foo {...}
(and rakudo might now accept this too).
You don't want to use augment for thi
On Mon, Feb 1, 2010 at 17:46, Patrick R. Michaud wrote:
> There's a third way:
>
>class B { ... }# introduce B as a class name without definition
> class A { sub foo { B::bar } }
>
>class B { sub bar { A::foo } }
>
> The first line is a literal "..." in the body of the class -- it
Patrick (>), Carl (>>):
>> I found two ways. Either one uses C (the language construct
>> formerly known as C):
>>
>> class B {}
>> class A { sub foo { B::bar } }
>> augment class B { sub bar { A::foo } }
>>
>> ...or one may use the C<::> notation to index a type using a string value:
>>
>>
On Sun, Jan 31, 2010 at 06:35:14PM +0100, Carl Mäsak wrote:
> I found two ways. Either one uses C (the language construct
> formerly known as C):
>
> class B {}
> class A { sub foo { B::bar } }
> augment class B { sub bar { A::foo } }
>
> ...or one may use the C<::> notation to index a type
Moritz (>), Carl (>>):
>> But on another level, the level of types, Perl 6 makes it fairly
>> *un*natural that the type C refers to the type C, which in
>> turn refers to the type C.
>
> True, and that has also been bothering me quite a bit.
>
> The "solution" is to always write ::Typename instead
Carl Mäsak wrote:
> But on another level, the level of types, Perl 6 makes it fairly
> *un*natural that the type C refers to the type C, which in
> turn refers to the type C.
True, and that has also been bothering me quite a bit.
The "solution" is to always write ::Typename instead of Typename...
uestion: How should M call out to R when R already calls out
to M?
The one-pass answer to both these questions are: "Well, you simply
need to force your types into a tree structure, and take special care
every time there's a forwards reference somewhere in all your modules.
Either define a
On Friday, 13. February 2009 20:30:24 Larry Wall wrote:
> While taking a shower I refined the design somewhat in my head,
> thinking about the ambiguities in package names when you're redefining.
> By my previous message, it's not clear whether the intent of
>
> multi package Foo::Bar {...}
>
>
Larry Wall wrote:
> Jon Lang wrote:
> : And with package versioning, you may not need an "is instead"
> : equivalent: if you want to "redefine" a package, just create a newer
> : version of it in a tighter lexical scope than the original package was
> : in. You can still access the original packag
On Fri, Feb 13, 2009 at 10:46:42AM -0800, Jon Lang wrote:
: And with package versioning, you may not need an "is instead"
: equivalent: if you want to "redefine" a package, just create a newer
: version of it in a tighter lexical scope than the original package was
: in. You can still access the o
Larry Wall wrote:
> Jon Lang wrote:
> : Well, we _do_ have a mechanism in place for adding to an existing
> : class (e.g., "class Foo is also { ... }"), and classes are a special
> : case of modules; so I don't see why you shouldn't be able to do
> : likewise with modules and even packages. That s
On Fri, Feb 13, 2009 at 09:44:12AM -0800, Jon Lang wrote:
: TSa wrote:
: > Does that imply that packages behave like C++ namespaces? That is
: > a package can be inserted into several times:
: >
: > package A
: > {
: > class Foo {...}
: > }
: > # later elsewhere
: > package A
: >
TSa wrote:
> Does that imply that packages behave like C++ namespaces? That is
> a package can be inserted into several times:
>
> package A
> {
> class Foo {...}
> }
> # later elsewhere
> package A
> {
> class Bar {...}
> }
>
> I would think that this is just different sy
On Fri, Feb 13, 2009 at 06:27:07PM +0100, TSa wrote:
> Does that imply that packages behave like C++ namespaces? That is
> a package can be inserted into several times:
>
>package A
>{
>class Foo {...}
>}
># later elsewhere
>package A
>{
>class Bar {...}
>
HaloO,
Jon Lang wrote:
Carl Mäsak wrote:
* A should be treated as a post-declared package.
Whatever this means, it sounds preferable. :)
It means that you can define package A without ever declaring it, by
declaring all of its contents using such statements as 'role A::B ',
'sub A::Foo', and
On Feb 11, 2009, at 2:46 PM, Carl Mäsak wrote:
Jon (>), Jonasthan (>>):
If we declared, for example:
role A::B {};
Then what should a reference to A be here? At the moment, Rakudo
treats it
as a post-declared listop, however I suspect we should be doing
something a
bit smarter? If so, w
Carl Mäsak wrote:
>> * A should be treated as a post-declared package.
>
> Whatever this means, it sounds preferable. :)
It means that you can define package A without ever declaring it, by
declaring all of its contents using such statements as 'role A::B ',
'sub A::Foo', and so on.
--
Jonathan
Jon (>), Jonasthan (>>):
>> If we declared, for example:
>>
>> role A::B {};
>>
>> Then what should a reference to A be here? At the moment, Rakudo treats it
>> as a post-declared listop, however I suspect we should be doing something a
>> bit smarter? If so, what should the answer to ~A.WHAT be?
>
On Wed, Feb 11, 2009 at 12:15 PM, Jonathan Worthington
wrote:
> Hi,
>
> If we declared, for example:
>
> role A::B {};
>
> Then what should a reference to A be here? At the moment, Rakudo treats it
> as a post-declared listop, however I suspect we should be doing something a
> bit smarter? If so,
Hi,
If we declared, for example:
role A::B {};
Then what should a reference to A be here? At the moment, Rakudo treats
it as a post-declared listop, however I suspect we should be doing
something a bit smarter? If so, what should the answer to ~A.WHAT be?
Thanks,
Jonathan
# New Ticket Created by Chris Dolan
# Please include the string: [perl #60384]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60384 >
The attached patch does s{__get_}{get_} on compilers/pge/PGE/
Match.pir to make POD matc
On Wed Sep 03 21:07:57 2008, s1n wrote:
> The List !flatten method does not properly recurse into references.
> List.pir:188 retrieves the elements opcode and does not check the pmc type
> for recursion.
>
> This functionality is needed for .elems and :prefix<+> to function
# New Ticket Created by "jason switzer"
# Please include the string: [perl #58560]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58560 >
The List !flatten method does not properly recurse into references.
On Fri, Jun 6, 2008 at 1:56 AM, chromatic <[EMAIL PROTECTED]> wrote:
> On Thursday 05 June 2008 19:43:40 Will Coleda wrote:
>
>> $ ack '\.gif' docs/book
>> docs/book/ch07_architecture.pod
>> 89:F
>>
>> but this file isn't in the repository. We should either pull the
>> reference, grab the image, or
On Thursday 05 June 2008 19:43:40 Will Coleda wrote:
> $ ack '\.gif' docs/book
> docs/book/ch07_architecture.pod
> 89:F
>
> but this file isn't in the repository. We should either pull the
> reference, grab the image, or come up with a substitute.
I have the file, but I'm not sure what the copyri
# New Ticket Created by Will Coleda
# Please include the string: [perl #55374]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=55374 >
$ ack '\.gif' docs/book
docs/book/ch07_architecture.pod
89:F
but this file isn't in the
On Fri, Apr 11, 2008 at 05:08:58PM -0400, Bob Rogers wrote:
: I don't see that this is any harder; unless I'm misunderstanding you,
: this is just another normal closure usage case. The OUTER scope is
: always the one defined by outersub, no matter how many calls back in the
: dynamic chain it mig
From: "John M. Dlugosz" <[EMAIL PROTECTED]>
Date: 11 Apr 2008 20:12:41 -
. . .
What happens? The OUTER scope no longer exists at CALL 3. Does a
symbolic reference to OUTER require that the entire scope be
retained, just in case? If "OUTER" itself (or OUTER::OUTER::...) is
OUTER::<$varname> (S06, "Out-of-scope names")
$OUTER::varname (S02, "Names")
specifies the $varname declared in the lexical scope surrounding the current
lexical scope (i.e. the scope in which the current block was defined).
sub outersub ()
{
my $a;
my $b;
my $closure = sub {
say $a; #
Hi all,
Thanks for the answers to my previous questions. I do appreciate it.
Today's stumper is this:
sub decode([EMAIL PROTECTED]) returns Array {
gather {
for @list -> $elem {
take $elem.isa(Array) ?? $elem[1] xx $elem[0] !! $elem;
}
}
}
dec
Mark Stosberg wrote:
>
> &::($meth)(self:);
Well, audreyt just made this work (r12960), which I what I what
I thought should work in the first place:
self.$meth().
So I'm happy. (But my curiosity about the spec for symbolic refs and OO
still stands. )
Mark
In reading about symbolic references, I didn't find any specific
language that mentioned using them in conjunction with methods or OO. I
would like to see specific language and examples added to the spec to
clarify this.
Here's a specific example which currently doesn't wor
t; : which I need to go stare at for a bit before replying. :-)
>
> This is tangentially related, but we might need to think about
> something like typed references in any event to enable various forms
> of round-trip language interoperability. That is, we could have
> refe
Er, read.
;-) It's in my task list, I'll try and get onto it soon.
>I imagined that the references would only ever be to -PMC- registers...?
I wouldn't have thought so. I thought in Perl 6 the lowercased types
like
"int" were to go in the I registers.
Yes...
I thin
n't look particularly general. I guess leo will
> know if there is something I've missed - leo, thoughts? I guess such a
> mechanism probably shouldn't be much work to implement, though, and would
> certainly be a nice, clean answer.
Words I love to hear. Er, read.
>
"Chip Salzenberg" <[EMAIL PROTECTED]> wrote:
On Tue, Jan 24, 2006 at 03:52:39PM -, Jonathan Worthington wrote:
"Chip Salzenberg" <[EMAIL PROTECTED]> wrote:
>The trick is to keep references to registers in a way that notices
>when the register set is
jeepers I mangled this paragraph
On Tue, Jan 24, 2006 at 10:31:50AM -0800, Chip Salzenberg wrote:
> What I had in mind, was imitating whatever a closure does to hold onto a
> context chain. I would detail that here except it's not on the top of my
> brain except (1) the point is the imitation-rat
On Tue, Jan 24, 2006 at 03:52:39PM -, Jonathan Worthington wrote:
> "Chip Salzenberg" <[EMAIL PROTECTED]> wrote:
> >The trick is to keep references to registers in a way that notices
> >when the register set is gone, or alternatively, that keeps the
> >regi
tangentially related, but we might need to think about
something like typed references in any event to enable various forms
of round-trip language interoperability. That is, we could have
references that are polymorphic depending on language context,
so that different behaviors can be emulated depending
"Paolo Molaro" <[EMAIL PROTECTED]> wrote:
On 01/24/06 Jonathan Worthington wrote:
.NET has these managed reference thingies. They're basically like
They are called managed pointers.
Yes. And now I've misled Parrot folks into mis-naming them managed
references.
ire restructuring the VM by e.g. adding a
register type.
This is good news, and the kinda solution I was hoping for. :-)
The trick is to keep references to registers in a way that notices
when the register set is gone, or alternatively, that keeps the
register set from going away. The latter i
On 01/24/06 Jonathan Worthington wrote:
> .NET has these managed reference thingies. They're basically like
They are called managed pointers.
> pointers, but safe. What makes them safe is that only certain instructions
> can create them and the pointer value can't be set directly (we can do t
"Nicholas Clark" <[EMAIL PROTECTED]> wrote:
On Tue, Jan 24, 2006 at 12:11:14AM -, Jonathan Worthington wrote:
.NET has these managed reference thingies. They're basically like
b) Add a v-table flag saying "returning me is forbidden" and checking
that
on any PMCs that get returned. (H
On Tue, Jan 24, 2006 at 12:11:14AM -, Jonathan Worthington wrote:
> .NET has these managed reference thingies. They're basically like
> b) Add a v-table flag saying "returning me is forbidden" and checking that
> on any PMCs that get returned. (However, there are subtle issues. For
> e
by e.g. adding a
register type.
The trick is to keep references to registers in a way that notices
when the register set is gone, or alternatively, that keeps the
register set from going away. The latter is already achieved by the
default LexPad implementation.
Therefore, the representation of a
e current method
2) Stash that reference somewhere so it lasts longer than the current
method's context does, or just return it
3) Assigns to that reference later => BANG! Segfault, or perhaps controlled
scribbling to evade security policies etc
Under .NET we have info to track statically
On Sat, Jan 21, 2006 at 10:37:40AM -0700, Joshua Choi wrote:
: Supposed I wanted to refer to $.head using a symbolic reference--how
: would I do it?
:
: my $varname = 'head';
: #1 say $.::($varname);
: #2 say $::('.' ~ $varname);
: #3 something else
I'd say #1 is easiest to grok, insofar
Supposed I wanted to refer to $.head using a symbolic reference--how
would I do it?
my $varname = 'head';
#1 say $.::($varname);
#2 say $::('.' ~ $varname);
#3 something else
# New Ticket Created by jerry gay
# Please include the string: [perl #37956]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37956 >
it seems a grep for 'cvs' returns a number of references in the parrot
sourc
On Wed, Oct 19, 2005 at 03:02:14PM +0200, TSa wrote:
: HaloO,
:
: Juerd wrote:
: >Luke Palmer skribis 2005-10-18 11:57 (-0600):
: >
: >>It looks nicer if you use the indirect object form:
: >> trans "string": [
: >>=> "0",
: >> ];
: >
: >
: >It'd also look very nice with optional paren
On Wed, Oct 19, 2005 at 01:48:08PM +0200, TSa wrote:
: HaloO,
:
: Luke Palmer wrote:
: >It looks nicer if you use the indirect object form:
: >
: >trans "string": [
: > => "0",
: >];
:
: Given the right interpretation this just looks like
: a typed label selection in a multi metho
HaloO,
Juerd wrote:
Luke Palmer skribis 2005-10-18 11:57 (-0600):
It looks nicer if you use the indirect object form:
trans "string": [
=> "0",
];
It'd also look very nice with optional parens:
"string".trans [ => "0" ];
Or is it not yet time to resuggest that? :)
I l
HaloO,
Luke Palmer wrote:
It looks nicer if you use the indirect object form:
trans "string": [
=> "0",
];
Given the right interpretation this just looks like
a typed label selection in a multi method.
multi trans
{
Str $x: ...; return;
Int $x: ...; return;
On 10/18/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
>
> Uh, no. Certainly not for a method. For a bare sub that has been
> predeclared it may be possible. But we don't want to remagicalize
> pairs after we just argued the heck out of it to make pairs *always*
> be named parameters.
My thought was
Luke Palmer skribis 2005-10-18 11:57 (-0600):
> It looks nicer if you use the indirect object form:
> trans "string": [
> => "0",
> ];
It'd also look very nice with optional parens:
"string".trans [ => "0" ];
Or is it not yet time to resuggest that? :)
Juerd
--
http://co
On 10/18/05, Eric <[EMAIL PROTECTED]> wrote:
> Currently we (can|will be able to) do
>
> "string".trans( (['h','e'] => "0") );
> "string".trans( <== ['h','e'] => "0");
>
> Those are fine and i can live with that, but it seems that if we made the
> signature of trans
>
> method trans(Str $self: [EMA
I have a suggestion/proposal/whatever.
I am just starting to get a grasp of uses for pairs and where they are
handy. Working on string.trans some showed that it would be useful to have
the function accept a list of pairs. That was working until the fix for
magical pairs went through and now the pa
[EMAIL PROTECTED] (Eric) writes:
>> On Fri, 14 Oct 2005 08:38:55 +0200, Peter Makholm <[EMAIL PROTECTED]>
>> wrote:
>> > Yesterday I spend some hours getting pugs to understand
>> > translitterations with multiple ranges in each pair. E.g.
> Actually its been fixed already. Of course i think the
On 16 Oct 2005 03:46:25 -, David Formosa (aka ? the Platypus) <
[EMAIL PROTECTED]> wrote:
>
> On Fri, 14 Oct 2005 08:38:55 +0200, Peter Makholm <[EMAIL PROTECTED]>
> wrote:
> > Yesterday I spend some hours getting pugs to understand
> > translitterations with multiple ranges in each pair. E.g.
On Fri, 14 Oct 2005 08:38:55 +0200, Peter Makholm <[EMAIL PROTECTED]> wrote:
> Yesterday I spend some hours getting pugs to understand
> translitterations with multiple ranges in each pair. E.g.
>
> "foobar".trans( "a-z" => "n-za-n" );
>
> By accident I tested something like:
>
> "foobar".t
On Fri, Oct 14, 2005 at 05:17:48PM -0700, Larry Wall wrote:
> form of tr/// should always use lists, with a helper function to
> translate "a..z" to a list and also carp about the fact that it will
> break under Unicode. :-)
And EBCDIC.
The dinosaurs are not extinct yet. I guess that they are t
[EMAIL PROTECTED] (Larry Wall) writes:
> : my %transtable;
> : for %intable.kv -> $k, $v {
> : # $k is stringified by the => operator.
>
> Interesting comment. I wonder if it's true.
That was my attempt to explain the observations I did. Clearly I put
the blame the wr
On Sat, Oct 15, 2005 at 01:27:58AM +0200, Juerd wrote:
: Larry Wall skribis 2005-10-14 10:43 (-0700):
: > Actually, it looks like the bug is probably that => is forcing
: > stringification on its left argument too agressively. It should only
: > do that for an identifier.
:
: Would it work to cal
On Fri, Oct 14, 2005 at 08:49:50PM +0200, Peter Makholm wrote:
: The code I'm lookin at is in pugs/src/perl6/Prelude.pm around line 380:
:
: method trans (Str $self: *%intable) is primitive is safe {
:
: my sub expand (Str $string is copy) {
: ...
: }
:
:
Larry Wall skribis 2005-10-14 10:43 (-0700):
> Actually, it looks like the bug is probably that => is forcing
> stringification on its left argument too agressively. It should only
> do that for an identifier.
Would it work to call this process autoquoting, instead of
stringification? I'm assumin
[EMAIL PROTECTED] (Larry Wall) writes:
> On Fri, Oct 14, 2005 at 08:38:55AM +0200, Peter Makholm wrote:
> : Yesterday I spend some hours getting pugs to understand
> : translitterations with multiple ranges in each pair. E.g.
> :
> : "foobar".trans( "a-z" => "n-za-n" );
> :
> : By accident I
On Fri, Oct 14, 2005 at 08:38:55AM +0200, Peter Makholm wrote:
: Yesterday I spend some hours getting pugs to understand
: translitterations with multiple ranges in each pair. E.g.
:
: "foobar".trans( "a-z" => "n-za-n" );
:
: By accident I tested something like:
:
: "foobar".trans( ['a' ..
Yesterday I spend some hours getting pugs to understand
translitterations with multiple ranges in each pair. E.g.
"foobar".trans( "a-z" => "n-za-n" );
By accident I tested something like:
"foobar".trans( ['a' .. 'z'] => "n-za-m" );
and it didn't work.
The problem is that ['a' .. 'z'] gets
Juerd wrote:
$y() = 7;
No, sorry, that looks to me as if $y is a reference to an lvalue sub,
not like any form of referencing of scalars.
I think it will come naturally to the C++ and Java folks. There the
accessor kind of functions is either mapped into the name get_y()
and set_y(value), or
On Thu, Jun 02, 2005 at 10:45:45PM +0200, Juerd wrote:
> If we allow "sub .foo", "sub :foo" comes naturally, and another
> asymmetry is gone.
>
> It would also allow "multi sub" and "multi method" to simply become
> "multi".
I _really_ like the explicit 'method' name that methods have. Calling
t
"TSa (Thomas Sandlaß)" skribis 2005-06-02 22:22 (+0200):
> The only thing that is a bit unclear to me is if the dot is part of the
> operator name---like a sigil---or purely syntactical. A method is e.g.
> also not defined with the dot:
> class Blahh
> {
>method .example ( $non_invocant ) {...}
1 - 100 of 319 matches
Mail list logo
