Richard,
That is a nice summary of some differences among various Callables.
Rob
On Tue, Aug 30, 2022 at 09:34:01PM +0100, Richard Hainsworth wrote:
> Hi Todd,
>
> Long time no see.
>
> Re your 'keeper'. There is a reason why things are called the way they are
> in Raku (aka Perl6). BEGIN is
On 9/4/22 04:23, Ralph Mellor wrote:
On Sun, Sep 4, 2022 at 5:07 AM ToddAndMargo via perl6-users
wrote:
For the fun of it, I placed a "booboo;"
Interesting!
You might like to think of `BEGIN` as a signal to the "compiler":
"Please do more than just "compile" this code. Please also run it,
On Sun, Sep 4, 2022 at 5:07 AM ToddAndMargo via perl6-users
wrote:
>
> For the fun of it, I placed a "booboo;"
>
> Interesting!
You might like to think of `BEGIN` as a signal to the "compiler":
"Please do more than just "compile" this code. Please also run it,
right now, before "compiling" any
On 9/2/22 18:14, ToddAndMargo via perl6-users wrote:
On 9/2/22 13:52, ToddAndMargo via perl6-users wrote:
On 9/2/22 00:13, ToddAndMargo via perl6-users wrote:
Found something interesting
$ raku -c GetUpdates.pl6
Syntax OK
Will execute the BEGIN {}, not just
syntax check it.
The guys on the
On 9/2/22 13:52, ToddAndMargo via perl6-users wrote:
On 9/2/22 00:13, ToddAndMargo via perl6-users wrote:
Found something interesting
$ raku -c GetUpdates.pl6
Syntax OK
Will execute the BEGIN {}, not just
syntax check it.
The guys on the chat line said this is normal
as `BEGIN` runs a
ck it.
>
> The guys on the chat line said this is normal
> as `BEGIN` runs a compile time
How short *is* your memory?
> From: Elizabeth Mattijsen
> Subject: Re: BEGIN {} question
> Date: 29 August 2022 at 09:44:30 CEST
> To: ToddAndMargo via perl6-users
>
>> Question, wo
On 9/2/22 00:13, ToddAndMargo via perl6-users wrote:
Found something interesting
$ raku -c GetUpdates.pl6
Syntax OK
Will execute the BEGIN {}, not just
syntax check it.
The guys on the chat line said this is normal
as `BEGIN` runs a compile time
--
~~
Found something interesting
$ raku -c GetUpdates.pl6
Syntax OK
Will execute the BEGIN {}, not just
syntax check it.
On 9/1/22 20:16, Andinus via perl6-users wrote:
ToddAndMargo via perl6-users @ 2022-09-01 10:30 -07:
On 9/1/22 00:45, Richard Hainsworth wrote:
Treat the regexes as data for a program. Compile the program once.
Run the regexes as often as you need.
Please elucidate. That could save me
ToddAndMargo via perl6-users @ 2022-09-01 10:30 -07:
> On 9/1/22 00:45, Richard Hainsworth wrote:
>> Treat the regexes as data for a program. Compile the program once.
>> Run the regexes as often as you need.
>
> Please elucidate. That could save me boat loads
> of time.
You could take the
On 9/1/22 00:45, Richard Hainsworth wrote:
Raku and Perl are two different languages in the same family. They
evolved with different targets, perl to react quickly to internet
requests, Raku to be a better programming language. This may not be the
take the actual developers have, but it's what
On 9/1/22 00:45, Richard Hainsworth wrote:
Work with Raku rather than expect it to be the same as Perl.
Oh I intent too! I program in Top Down. Perl 5's
subroutines are a nightmare. I ADORE Perl 6's subroutines.
By saying above / below, this indicates a linear view of
code at the same
On Wed, 31 Aug 2022, 00:59 ToddAndMargo via perl6-users, <
perl6-users@perl.org> wrote:
> On 8/30/22 13:34, Richard Hainsworth wrote:
> > Hi Todd,
> >
>
> > Since you continue for ever to complain about 'compile' time issues,
>
> "Stage parce" is specifically what I am whining about
>
> > rather
On 8/30/22 13:34, Richard Hainsworth wrote:
Hi Todd,
Long time no see.
Re your 'keeper'. There is a reason why things are called the way they
are in Raku (aka Perl6). BEGIN is NOT a special subroutine.
BEGIN is a phaser. And it introduces a block. Blocks are not subroutines
(subs). Even
Hi Todd,
Long time no see.
Re your 'keeper'. There is a reason why things are called the way they
are in Raku (aka Perl6). BEGIN is NOT a special subroutine.
BEGIN is a phaser. And it introduces a block. Blocks are not subroutines
(subs). Even though blocks and subs (and methods and
On 8/28/22 15:58, ToddAndMargo via perl6-users wrote:
Hi All,
I am thinking of using
BEGIN {}
to fire up a splash screen (libnotify).
Question: is what happens between the brackets
isolated from the rest of the code? If I set
variable values or declare variables, are they
wiped out,
On 8/29/22 13:03, ToddAndMargo via perl6-users wrote:
On 8/28/22 15:58, ToddAndMargo via perl6-users wrote:
Hi All,
I am thinking of using
BEGIN {}
to fire up a splash screen (libnotify).
Question: is what happens between the brackets
isolated from the rest of the code? If I set
On 8/28/22 15:58, ToddAndMargo via perl6-users wrote:
Hi All,
I am thinking of using
BEGIN {}
to fire up a splash screen (libnotify).
Question: is what happens between the brackets
isolated from the rest of the code? If I set
variable values or declare variables, are they
wiped out,
On 8/29/22 10:45, Tom Browder wrote:
On Mon, Aug 29, 2022 at 12:31 PM ToddAndMargo via perl6-users
wrote:
On 8/29/22 08:41, Tom Browder wrote:
...
And I think you may be surprised how much speedup you may get by using
the precompiled-module "trick" for most of your 11,000-line program.
...
On Mon, Aug 29, 2022 at 12:31 PM ToddAndMargo via perl6-users
wrote:
> On 8/29/22 08:41, Tom Browder wrote:
...
> > And I think you may be surprised how much speedup you may get by using
> > the precompiled-module "trick" for most of your 11,000-line program.
...
> Hi Tom,
> The .precomp
On 8/29/22 08:41, Tom Browder wrote:
On Mon, Aug 29, 2022 at 10:29 AM ToddAndMargo via perl6-users
mailto:perl6-users@perl.org>> wrote:
...
> Does the compiler make a full pass through
> the code before firing off the BEGIN routine
NO.
And I think you may be surprised how much speedup you
On Mon, Aug 29, 2022 at 10:29 AM ToddAndMargo via perl6-users <
perl6-users@perl.org> wrote:
...
> Does the compiler make a full pass through
> the code before firing off the BEGIN routine
NO.
And I think you may be surprised how much speedup you may get by using the
precompiled-module "trick"
On 8/29/22 00:44, Elizabeth Mattijsen wrote:
Question, would BEGIN go at the top or the bottom
of my code? Seems the compiler would hit it first
at the top, but I do not know if it makes a full
pass of everything before firing off the BEGIN.
BEGIN runs at *compile* time.
This means that
> Question, would BEGIN go at the top or the bottom
> of my code? Seems the compiler would hit it first
> at the top, but I do not know if it makes a full
> pass of everything before firing off the BEGIN.
BEGIN runs at *compile* time.
This means that anything before the BEGIN statement in the
On 8/28/22 19:11, Bruce Gray wrote:
On Aug 28, 2022, at 5:58 PM, ToddAndMargo via perl6-users
wrote:
Hi All,
I am thinking of using
BEGIN {}
to fire up a splash screen (libnotify).
Question: is what happens between the brackets
isolated from the rest of the code? If I set
variable
> On Aug 28, 2022, at 5:58 PM, ToddAndMargo via perl6-users
> wrote:
>
> Hi All,
>
> I am thinking of using
>
> BEGIN {}
>
> to fire up a splash screen (libnotify).
>
> Question: is what happens between the brackets
> isolated from the rest of the code? If I set
> variable values or
Hi All,
I am thinking of using
BEGIN {}
to fire up a splash screen (libnotify).
Question: is what happens between the brackets
isolated from the rest of the code? If I set
variable values or declare variables, are they
wiped out, etc.?
Many thanks,
-T
--
27 matches
Mail list logo
