On 2021-01-05 David Emanuel da Costa Santiago
wrote:
> > so the inner ``whenever`` really sets up a separate tap every time
> > it's executed.
> Is this behaviour expected? It kinda looks weird to me, specially
> when looking to the output...
Well, it's what *I* expected: a ``whenever`` sets
Às 13:25 de 05/01/21, Gianni Ceccarelli escreveu:
>
>received outer 0
>received outer 1
>received outer 2
>received outer 3
>received inner 0 for outer 0
>received inner 0 for outer 1
>received inner 0 for outer 2
>received inner 0 for outer 3
>received inner
Can you try 'mkdir' manually beforehand to create the desired
'/usr/share/perl6/site/doc' directory, then run 'zef install p6doc' ?
Just wondering... . I note your other comments with great interest.
Best, Bill.
On Tue, Jan 5, 2021 at 9:02 AM Gianni Ceccarelli
wrote:
> On 2021-01-05 William Mi
Yep, there are a couple of (known) issues here:
https://github.com/Raku/problem-solving/issues/252 which request to remove
it from the ecosystem (and I'll probably do it when I finish this email),
and this one https://github.com/Raku/doc/issues/2896 Build.pm does not
really work now, to it should p
On 2021-01-05 William Michels via perl6-users
wrote:
> Raiph's suggestion works for me (on rakudo-2020.10). I mean, p6doc
> installs
Oh, that points to new, different, problems.
https://modules.raku.org/search/?q=p6doc links to
https://github.com/Raku/doc which does not contain a ``p6doc`` scrip
They are tested for compilation, not that they generate the desired
results (though this is a wishlist item in the docs backlog)
On Tue, Jan 5, 2021 at 9:59 AM Ralph Mellor wrote:
>
> Sounds to me like it's time to raise a doc issue.
>
> Also, does anyone know if doc examples are tested?
>
> No
On Tue, Jan 5, 2021 at 5:10 AM Ralph Mellor wrote:
>
> I googled rakudoc and that led to:
>
> https://github.com/Raku/rakudoc
>
> which says it's forked from:
>
> https://github.com/noisegul/perl6-p6doc
>
> So I tried that in m.r.o and it's listed:
>
> https://modules.raku.org/search/?q=p6doc
>
>
And here it comes again, the common mess about Raku and Rakudo. :)
The point is that Rakudo doesn't come bundled with documentation about Raku
because the former just implements the latter. It's not like it is with perl
where `perl` binary and `Perl` are the same and `perl -v` is your current
Sounds to me like it's time to raise a doc issue.
Also, does anyone know if doc examples are tested?
Not just when first published, but as part of blinning?
On Tue, Jan 5, 2021 at 1:30 PM Theo van den Heuvel
wrote:
>
> Hi gurus,
>
> The first example in the documentation on the start control
On 2021-01-05 Brad Gilbert wrote:
> There really shouldn't be that much difference between what the
> documentation says and how your version works.
I've worked on machines stuck with perl 5.8 when the online
documentation was for 5.26
I'd like to live in a world where:
* raku is popular and wi
There really shouldn't be that much difference between what the
documentation says and how your version works.
The biggest thing would be new functions that you don't have yet.
(Which you could just copy the code from the sources into your program if
you need them.)
Even if rakudoc did install, i
What is happening is that the `start` happens on another thread.
That thread is not the main thread.
The program exits when the main thread is done.
Since the main thread doesn't have anything else to do it exits before that
`sleep` is done.
The more correct way to handle it would be to wait for
thanks. That helps.
Elizabeth Mattijsen schreef op 2021-01-05 14:37:
If those are the only lines in your program, the program will have
exited before the sleep in the start has actually passed. If you
change the program to:
start { sleep 1; say "done"; exit }
say "working";
sleep;
If those are the only lines in your program, the program will have exited
before the sleep in the start has actually passed. If you change the program
to:
start { sleep 1; say "done"; exit }
say "working";
sleep;
you should also see the "done".
> On 5 Jan 2021, at 14:15, Theo van
On 2021-01-05 JJ Merelo wrote:
> Gianni is basically right. rakudoc has not really been released yet
> into the ecosystem, and p6doc will get you the documentation itself,
> which you will have to build then. So LTA is true, and there's some
> work to be done. There's probably an issue already cre
Hi gurus,
The first example in the documentation on the start control flow does
not seem to work as promised.
Here is the code:
start { sleep 1; say "done" }
say "working";
# working, done
Both 2020.1 and the 2020.12 version under Ubuntu yield only "working".
Am I missing something?
--
The
Gianni is basically right. rakudoc has not really been released yet into
the ecosystem, and p6doc will get you the documentation itself, which you
will have to build then. So LTA is true, and there's some work to be done.
There's probably an issue already created, but it will pop up if you create
a
I googled rakudoc and that led to:
https://github.com/Raku/rakudoc
which says it's forked from:
https://github.com/noisegul/perl6-p6doc
So I tried that in m.r.o and it's listed:
https://modules.raku.org/search/?q=p6doc
So, perhaps you can zef install p6doc?
Maybe the doc you read mentioning
On 2020-12-30 Gianni Ceccarelli wrote:
> Also, my understanding of ``whenever`` is that it's adding a hook into
> the event loop, and only leaving the surrounding ``react`` (or
> ``supply``) will remove that hook (people who understand this better
> than I do: please correct me!). If that's true,
https://docs.raku.org/programs/02-reading-docs says to use ``rakudoc``
to read the documentation of installed modules.
I don't have it installed::
$ rakudoc
-bash: rakudoc: command not found
Not a problem, that same page says to use zef::
$ $ zef install rakudoc
===> Searching for: raku
20 matches
Mail list logo
