On Thu, 09 Mar 2017 12:55:58 -0800, zef...@fysh.org wrote:
> Brandon Allbery via RT wrote:
> >Erm. Isn't Nil a silent Failure?
>
> It may well represent such a thing, but it is also a reified object.
> Putting objects into sets is an operation that's applicable to any kind
> of object, and which (
On Fri, 25 Aug 2017 18:56:37 -0700, alex.jakime...@gmail.com wrote:
> The input file for this problem is ≈15 MB so please bear with external
> link:
> https://files.progarm.org/golfed.gz (1.6 MB compressed)
>
> Command:
> perl6 -ne 'say $++' golfed
> # or
> perl6 -ne 'say $++' < golfed
>
> Result
On Fri, 25 Aug 2017 18:56:37 -0700, alex.jakime...@gmail.com wrote:
> The input file for this problem is ≈15 MB so please bear with external
> link:
> https://files.progarm.org/golfed.gz (1.6 MB compressed)
>
> Command:
> perl6 -ne 'say $++' golfed
> # or
> perl6 -ne 'say $++' < golfed
>
> Result
On Mon, Sep 4, 2017 at 6:18 AM, Elizabeth Mattijsen wrote:
> That can not be relied on in general, I’m afraid. However, after some
> discussion, it appears that there is some support for an
> "is-initial-thread” method:
>
>https://irclog.perlgeek.de/perl6-dev/2017-09-04#i_15112552
>
> Note t
On Fri, 01 Sep 2017 20:15:07 -0700, alex.jakime...@gmail.com wrote:
> Command:
> # run it and then send SIGINT (e.g. with Ctrl+C)
> perl6 -e 'react whenever signal(SIGINT).merge(signal(SIGTERM)) { say
> ‘hey!’; exit 0 }'
>
> Result:
> hey!
>
>
> Command:
> # run it and then send SIGINT (e.g. wit
On Fri, 01 Sep 2017 20:15:07 -0700, alex.jakime...@gmail.com wrote:
> Command:
> # run it and then send SIGINT (e.g. with Ctrl+C)
> perl6 -e 'react whenever signal(SIGINT).merge(signal(SIGTERM)) { say
> ‘hey!’; exit 0 }'
>
> Result:
> hey!
>
>
> Command:
> # run it and then send SIGINT (e.g. wit
> On 4 Sep 2017, at 10:44, JuhiMarcel LangbroekTimmerman
> wrote:
> Thanks for your anwer. I assume there are a few things I can rely on;
> - the main thread is where the code starts and will always have id 1
That can not be relied on in general, I’m afraid. However, after some
discussion, it
Hi liz,
Thanks for your anwer. I assume there are a few things I can rely on;
- the main thread is where the code starts and will always have id 1
- a continuation of statements/blocks will always be excecuted on the same
thread except for those hyper thingies which are again separate blocks or
> On 4 Sep 2017, at 09:29, Marcel Timmerman wrote:
> I was wondering about the following,
>
> When an Exception is thrown in a thread and is CATCHed in another object,
> will that block be run in the same thread as the Exception is thrown?
I think from 6.d onward, you can not rely on your code
Hi,
I was wondering about the following,
When an Exception is thrown in a thread and is CATCHed in another
object, will that block be run in the same thread as the Exception is
thrown?
Thanks in advance,
Marcel
10 matches
Mail list logo
