Re: a question on use and . in class declarations

On 12/30/20 5:41 PM, ToddAndMargo via perl6-users wrote: A question on the "use" in a class declaration. In "use $.x". does the dot have a special meaning or is it just to make the value ($.x) easier to access ($objectname.x)? Many thanks, -T From my in progress notes on OOP: ***

Re: for and ^ question

On 12/30/20 7:06 PM, yary wrote: Look up ..^ which is the long form of ^ when used in ^8 sort of thing https://docs.raku.org/routine/..$CIRCUMFLEX_ACCENT "Constructs a Range  from the arguments, excluding

Re: for and ^ question

Look up ..^ which is the long form of ^ when used in ^8 sort of thing https://docs.raku.org/routine/..$CIRCUMFLEX_ACCENT "Constructs a Range from the arguments, excluding the end point." try out these 3 .. 7 3 ..^ 7 3 ^.. 7 3 ^..^ 7 and also see

Re: for and ^ question

On 12/30/20 6:04 PM, Curt Tilmes wrote: On Wed, Dec 30, 2020 at 8:40 PM ToddAndMargo via perl6-users wrote: In the following for loop: for ^$nCount -> $i { What is the ^ doing? https://docs.raku.org/type/Range About the third paragraph from the top: The caret is also a prefix

Re: for and ^ question

On 12/30/20 5:39 PM, ToddAndMargo via perl6-users wrote: Hi All, In the following for loop:     for ^$nCount -> $i { What is the ^ doing? Confused again, -T Used in context, the ^ makes the integer $nCount look like an array of 0 to ($nCount - 1). Am I missing something? my $x=4; for

Re: for and ^ question

On Wed, Dec 30, 2020 at 8:40 PM ToddAndMargo via perl6-users wrote: > In the following for loop: > > for ^$nCount -> $i { > > What is the ^ doing? https://docs.raku.org/type/Range About the third paragraph from the top: The caret is also a prefix operator for constructing numeric ranges

a question on use and . in class declarations

A question on the "use" in a class declaration. In "use $.x". does the dot have a special meaning or is it just to make the value ($.x) easier to access ($objectname.x)? Many thanks, -T

for and ^ question

Hi All, In the following for loop: for ^$nCount -> $i { What is the ^ doing? Confused again, -T

Re: Please take apart this stub line for me

On 12/30/20 2:52 AM, JJ Merelo wrote: I'm also requesting you to take these totally improductive questions (and subsequent discussions) elsewhere. I'm not participating in it any more. JJ, You are the one who hosed me and personally insulted me as well rather than either answering the

Re: Please take apart this stub line for me

On 12/30/20 2:49 AM, Veesh Goldman wrote: Todd, you're being mean. Please stop I will see what I can find in the Turkish section of Netflix. I still think an explanation of the line would be a fascinating insight into the inner working of Raku.

Re: Help with bug

Thanks for the explanation! A December 30, 2020 3:28:24 PM UTC, Gianni Ceccarelli escreveu: >On 2020-12-30 David Santiago wrote: >> Thanks! It's indeed much clearer. However i have a question, why the >> react on line 24? >> >> The react there isn't required right? > >I think it is ☺ The

Re: Help with bug

On 2020-12-30 David Santiago wrote: > Thanks! It's indeed much clearer. However i have a question, why the > react on line 24? > > The react there isn't required right? I think it is ☺ The code, without the debugging bits:: react { whenever $channel -> $val {

Re: Help with bug

Às 14:43 de 30/12/20, Gianni Ceccarelli escreveu: David: please look at my version of your code, I really think it's clearer and simpler to work with, without the explicit ``.tap`` and ``.then`` (ok, I have a few ``.then``, but they're for debugging, they don't affect the actual working of the

Re: Help with bug

Thank you for the compliment. But I was merely channeling Jonathan Worthington... :-) > On 30 Dec 2020, at 14:43, Gianni Ceccarelli wrote: > > Liz is, as usual, correct: there's no reason to wait until our write > buffers are flushed (``await $conn.print``) before ``react``ing to > what's in

Re: Help with bug

Liz is, as usual, correct: there's no reason to wait until our write buffers are flushed (``await $conn.print``) before ``react``ing to what's in our *read* buffers. In https://github.com/dakkar/raku-socket-test-from-demanuel I've removed all ``await`` but one (the ``await .connect``), and the

Re: Please take apart this stub line for me

El mié, 30 dic 2020 a las 11:40, ToddAndMargo via perl6-users (< perl6-users@perl.org>) escribió: > On 12/30/20 2:21 AM, JJ Merelo wrote: > > It's "hosing me down". No, I'm not doing that. Veesh's answer was good > > enough for me; it probably should be for you. > > > > Cheers > > > > JJ > > Hi

Re: Please take apart this stub line for me

Todd, you're being mean. Please stop On Wed, Dec 30, 2020, 12:40 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 12/30/20 2:21 AM, JJ Merelo wrote: > > It's "hosing me down". No, I'm not doing that. Veesh's answer was good > > enough for me; it probably should be for you. > > >

Re: Please take apart this stub line for me

On 12/30/20 2:21 AM, JJ Merelo wrote: It's "hosing me down". No, I'm not doing that. Veesh's answer was good enough for me; it probably should be for you. Cheers JJ Hi JJ, To Quote Veesh: No. I can't imagine that what you're doing now is productive. What are you actually

Re: Please take apart this stub line for me

It's "hosing me down". No, I'm not doing that. Veesh's answer was good enough for me; it probably should be for you. Cheers JJ

Re: Please take apart this stub line for me

On 12/30/20 1:44 AM, JJ Merelo wrote: El mié, 30 dic 2020 a las 10:14, ToddAndMargo via perl6-users (mailto:perl6-users@perl.org>>) escribió: On 12/30/20 12:18 AM, JJ Merelo wrote: > > > El mié, 30 dic 2020 a las 8:02, Veesh Goldman (mailto:rabbive...@gmail.com>

Re: Please take apart this stub line for me

El mié, 30 dic 2020 a las 10:14, ToddAndMargo via perl6-users (< perl6-users@perl.org>) escribió: > On 12/30/20 12:18 AM, JJ Merelo wrote: > > > > > > El mié, 30 dic 2020 a las 8:02, Veesh Goldman ( > >) escribió: > > > > No. > > I can't imagine that what

Re: Help with bug

Hi! Às 00:16 de 30/12/20, Elizabeth Mattijsen escreveu: react, feels like a code smell to me. An `await` will block the `react` block from processing other messages until the `await` returns. Which feels like it is opening up a large window of dead-locking opportunities. I changed the

Re: Please take apart this stub line for me

On 12/30/20 12:18 AM, JJ Merelo wrote: El mié, 30 dic 2020 a las 8:02, Veesh Goldman (>) escribió: No. I can't imagine that what you're doing now is productive. What are you actually trying to understand by reading the source. Probably proving his

Re: Please take apart this stub line for me

On 12/29/20 11:02 PM, Veesh Goldman wrote: No. I can't imagine that what you're doing now is productive. What are you actually trying to understand by reading the source. Veesh, My brain is wired differently that most other people and I presume yours as well. Does not make one brain

Re: Please take apart this stub line for me

El mié, 30 dic 2020 a las 8:02, Veesh Goldman () escribió: > No. > I can't imagine that what you're doing now is productive. > What are you actually trying to understand by reading the source. > Probably proving his point that anything, up to and including looking at clouds and watching Turkish