Thanks for the in-depth analysis. My misunderstanding was about what an
identifier considers a number; I have no well-thought-out ideas on the
subject of what an identifier ought to be.
Having the docs mention that "number" means only characters with a Unicode
Property GeneralCategory of Nd might
On Fri, May 20, 2016 at 09:39:30AM -0400, yary wrote:
: On Tue, Apr 12, 2016 at 6:12 PM, Brandon Allbery
: wrote:
: > I was explaining why some "symbols" are acceptable to the parser. Which
: one
: > is more appropriate is not my call,
:
: I was thinking about what exactly
To be clear, I expect that "number" in "followed by zero or more word
characters (alphabetic, underscore or number)" means "if Unicode thinks
it's numeric, you can use it in an identifier after the first character."
I don't expect that every numeric codepoint in Unicode must evaluate to
number in
On Tue, Apr 12, 2016 at 6:12 PM, Brandon Allbery
wrote:
> I was explaining why some "symbols" are acceptable to the parser. Which
one
> is more appropriate is not my call,
I was thinking about what exactly are valid identifiers in Perl6/rakudo's
implementation. The docs
On Tue, Apr 12, 2016 at 6:07 PM, Darren Duncan
wrote:
> On 2016-04-12 6:59 AM, Brandon Allbery wrote:
>
>> On Tue, Apr 12, 2016 at 9:51 AM, Brock Wilcox
>> wrote:
>> Heart doesn't work for me, but other symbols seem fine. I don't know
>>
On 2016-04-12 6:59 AM, Brandon Allbery wrote:
On Tue, Apr 12, 2016 at 9:51 AM, Brock Wilcox
wrote:
Heart doesn't work for me, but other symbols seem fine. I don't know why. I
also didn't need to quote them. Here is a REPL session from a Rakudo
2016.01.1:
If we don't want to get the "line noise" libel all over again, there
are some features of the language that should probably go unmentioned
for a while. The ability to use non-ASCII characters in names may be
perfectly justifiable. When the cognoscenti have produced enough
decent code showing how
Thanks again, I get it now.
Theo
Larry Wall schreef op 2016-04-12 17:00:
On Mon, Apr 11, 2016 at 11:32:29PM +0200, Theo van den Heuvel wrote:
: Thanks Larry for the answer and the great language.
:
: It is quite ok for me to start alphabetically. I use the funny char
: to indicate a particular
On Mon, Apr 11, 2016 at 11:32:29PM +0200, Theo van den Heuvel wrote:
: Thanks Larry for the answer and the great language.
:
: It is quite ok for me to start alphabetically. I use the funny char
: to indicate a particular aspect shared by a bunch of subs operators
: and methods.
: So I tried:
:
Heart doesn't work for me, but other symbols seem fine. I don't know why. I
also didn't need to quote them. Here is a REPL session from a
Rakudo 2016.01.1:
> sub Δ($x) { say "got $x" }
sub Δ ($x) { #`(Sub|106407520) ... }
> Δ(23)
got 23
> class Foo { method Δ($x) { say "method got $x" } }
>
@Parrot Raiser and @Luca. I will make sure to add Texan alternatives in
case other people need to take over.
I use triangle symbols to make internal symmetries in the code visible,
and I have no problem pronouning or typing them.
The code is substantially more readable with them. The same is
Mathematical symbols might be a legitimate case, since they are
generally pronounceable. Otherwise, special characters cause problems
both in entry from the keyboard and thinking about the code. (What
does it sound like if you describe it to yourself? foo.heart?)
On 4/12/16, Luca Ferrari
On Tue, Apr 12, 2016 at 9:44 AM, Theo van den Heuvel
wrote:
>
> Why? Perhaps you are confusing taste and good sense. The heart is just an
> example. My intention is for a mathematical symbol and a mathematical
> meaning. I see nothing wrong with that.
unless you have to
Why? Perhaps you are confusing taste and good sense. The heart is just
an example. My intention is for a mathematical symbol and a mathematical
meaning. I see nothing wrong with that.
Parrot Raiser schreef op 2016-04-12 01:06:
I hope I never run across code written by someone who thinks this
I hope I never run across code written by someone who thinks this is a
good idea.
On 4/11/16, Theo van den Heuvel wrote:
> Thanks Larry for the answer and the great language.
>
> It is quite ok for me to start alphabetically. I use the funny char to
> indicate a particular
Thanks Larry for the answer and the great language.
It is quite ok for me to start alphabetically. I use the funny char to
indicate a particular aspect shared by a bunch of subs operators and
methods.
So I tried:
method term: { "Mel G.".say }
However, that gives me:
Bogus postfix
You have to write it like this:
class Foo {
method ::('❤') { "mem heart".say }
}
my Foo $foo .= new;
$foo.'❤'();
Other than that, only names beginning alphabetically are allowed.
You could work around this on the caller end with a postfix:<❤>, but
that would be an
Hi Brock,
no, that gives me
Missing block
Theo
Brock Wilcox schreef op 2016-04-10 15:55:
Maybe try it without the term, just "method funnychar (..."
On Apr 10, 2016 09:23, "Theo van den Heuvel"
wrote:
Hi perl6 fans,
I can use funny characters in operators or in sub
Maybe try it without the term, just "method funnychar (..."
On Apr 10, 2016 09:23, "Theo van den Heuvel" wrote:
> Hi perl6 fans,
>
> I can use funny characters in operators or in sub names (using
> term:<...>). However, when I try the same thing with an operator as in:
>
>
Hi perl6 fans,
I can use funny characters in operators or in sub names (using
term:<...>). However, when I try the same thing with an operator as in:
class Foo {
method term:<❤> { "mem heart".say }
}
my Foo $foo .= new;
$foo.❤;
I get:
Malformed postfix call
That is unexpected for me,
20 matches
Mail list logo