Unfortunately, neither rendered constraints nor image insertions are
implemented yet. Or it is so up to my knowledge, at least. I miss these
features too sometimes.
Best regards,
Vadim Belman
> On Aug 31, 2020, at 6:56 AM, Fernando Santagata
> wrote:
>
> Hello *,
>
> I was wondering
Every time $ shows up, it is a different scalar.
$=1; say $;
is similar to
my $anonONE=1; say $anonTWO;
thus they are very limited use
-y
On Tue, Sep 1, 2020 at 3:55 PM Andy Bach
wrote:
> > My first clue that something is amiss is in your third line of code when
> the return skips "AA"
> My first clue that something is amiss is in your third line of code when the
> return skips "AA" and starts "AB, AC, AD". That suggests to me that the
> two step assign/printf call is playing havoc with the $ anonymous variable
Missed that about the missing AA - does the same thing with
My first clue that something is amiss is in your third line of code when
the return skips "AA" and starts "AB, AC, AD". That suggests to me
that the two step assign/printf call is playing havoc with the $ anonymous
variable. Try this instead:
~$ raku -e 'for -> $alpha { for (1..14) {
I'm barely hanging on with the "$" so ... so from:
raku -e 'for -> $alpha { for (1..14) { print (state $ = $alpha)++ ~ "
" } }'
AA AB AC AD AE AF
I tried an actual, er, non-anon var
# raku -e 'for -> $alpha { for (1..14) { print (state $sv = $alpha)++
~ " " } }'
AA AB AC AD AE AF ...
Yes, because INIT and BEGIN happen before runtime, and $alpha is set at
runtime! Hence my original BEGIN example using a constant to set the first
value.
Another reason to prefer "state" over those phasers... unless you want a
counter over the lifetime of the process, which is valid.
-y
On
I tried combining Larry's code and Yary's code, variously using
"state" or "INIT" or "BEGIN". This is what I saw:
~$ raku -e 'for -> $alpha { for (1..14) { print (state $ =
$alpha)++ ~ " " } }'
AA AB AC AD AE AF AG AH AI AJ AK AL AM AN NN NO NP NQ NR NS NT NU NV
NW NX NY NZ OA
~$ raku -e 'for
Hello all,
A Raku Steering Council will be elected to serve the needs of the
greater Raku Community. At present we are in the nomination period,
which will end on Sept. 6th at midnight UTC:
https://github.com/Raku/Raku-Steering-Council/blob/main/announcements/20200720.md
Are you interested in
Thanks, that's cool, and shows me something I was wondering about
On Tue, Sep 1, 2020 at 11:36 AM Larry Wall wrote:
> If you want to re-initialize a state variable, it's probably better to make
> it explicit with the state declarator:
>
> $ raku -e "for { for (1..2) { say (state $ =
On Mon, Aug 31, 2020 at 05:05:53PM -0700, yary wrote:
: I like this better for alpha counter
:
: raku -e "for (1..4) { say (BEGIN $ = 'AAA')++ }"
:
: with BEGIN, the assignment of AAA happens once. With the earlier ||= it
: checks each time through the loop.
: -y
Careful with that, though,
On 2020-09-01 11:14, ToddAndMargo via perl6-users wrote:
I see Fedora's docs -- which I use a lot -- uses
the same idea:
https://docs.fedoraproject.org/en-US/fedora/f32/system-administrators-guide/Wayland/
But somehow is a ton more obvious.
Reference page:
On Sun, Aug 30, 2020 at 03:12:26PM -0700, yary wrote:
: I have a quibble there. 1st & 2nd sentences disagree slightly by going from
: active to passive voice. "Caller, the one who calls" vs "object on which
: that method is being called"
:
: Suggestion for 2nd sentence "The invocant of a method
On 2020-08-31 21:48, ToddAndMargo wrote:
On 2020-08-30 08:16, yary wrote:
Looking up https://docs.raku.org/routine/lines shows a Table of
Contents with
class Cool
(Cool) routine lines
class Supply
(Supply) method lines
class Str
(Str) routine lines
class
On Tue, Sep 1, 2020 at 8:27 AM Brian Duggan wrote:
>
> On Monday, August 31, Bruce Gray wrote:
> > I finally settled on using `try` instead of numeric coercion, because
> > if I am not golfing, I think `try` makes the grep look more like
> > “filter out the non-numbers” instead of “get rid of the
On Monday, August 31, Bruce Gray wrote:
> I finally settled on using `try` instead of numeric coercion, because
> if I am not golfing, I think `try` makes the grep look more like
> “filter out the non-numbers” instead of “get rid of the zero values”.
Another option is to use 'val' -- which
Some comments on the linguist contribution.
While 'invocant' and 'invoker' may be 'functionally equivalent', it
seems to me that in fact 'invocant' is correct.
'Invocant' indicates a thing that invokes, and does not imply
necessarily an intent. By analogy, we have 'defendant' in normal
16 matches
Mail list logo
