Re: Raku IO IceDrive bug

On Oct 22, 2023, at 06:02, ToddAndMargo via perl6-users wrote: spurt "$TestFile", "Old File Found\n"; spurt "$TestFile", "New File Opened\n"; On 11/5/23 12:08, William Michels via perl6-users wrote: > Won't adding a `\n` newline to the `spurt()` call eventually cause > problems? > > What

Re: Raku IO IceDrive bug

Won't adding a `\n` newline to the `spurt()` call eventually cause problems? What happens if you omit the `\n` below? Best, Bill. > On Oct 22, 2023, at 06:02, ToddAndMargo via perl6-users > wrote: > > spurt "$TestFile", "Old File Found\n"; > spurt "$TestFile", "New File Opened\n";

Re: Raku IO IceDrive bug

On 10/21/23 20:50, Ralph Mellor wrote: Hi again. :) Let me try again. I'll try cover things more clearly. #1 There was/is a bug in your code, or at least code that you say isn't working on your system. (It works on glot.io. See #3) ``` $WanIpFileName.IO.open(:w); spurt

Re: Raku IO IceDrive bug

Hi again. :) Let me try again. I'll try cover things more clearly. #1 There was/is a bug in your code, or at least code that you say isn't working on your system. (It works on glot.io. See #3) ``` $WanIpFileName.IO.open(:w); spurt "$WanIpFileName", "New File Opened";

Re: Raku IO IceDrive bug

at it opens the file it's spurting to), and/or behavior due to your Windows file system / account settings that leads to the issue you see, and/or a bug in your code. Let me explain. Here's what the code does: 1. Opens the file with `$WanIpFileName.IO.open(:w);` if it doesn't already exist

Re: Raku IO IceDrive bug

purting to), and/or behavior due to your Windows file system / account settings that leads to the issue you see, and/or a bug in your code. Let me explain. Here's what the code does: 1. Opens the file with `$WanIpFileName.IO.open(:w);` if it doesn't already exist. 2. Opens the file with `spurt` an

Raku IO IceDrive bug

Hi All, Windows 10 22H2 Windows 11 22H2 RakudoMoar-2023.09.01-win-x86_64-msvc.msi https://github.com/AntonOks/rakudo-star-win/releases Note: zef requires git An IO bug with Windows Ice Drive to report. (I no longer report them the the bug reporter as I have zero luck.) Ice Drive is a cloud

Re: Is this a regex bug?

On 6/20/23 13:32, Bruce Gray wrote: On Jun 19, 2023, at 18:50, ToddAndMargo via perl6-users wrote: Hi All, Fedora 37 RakudoPkgFedora37-2023.05.01.x86_64.rpm https://github.com/nxadm/rakudo-pkg/releases The `/$0$1 $2/` is not coming out correct. Is this a bug or did I do something wrong

Re: Is this a regex bug?

> On Jun 19, 2023, at 18:50, ToddAndMargo via perl6-users > wrote: > > Hi All, > > Fedora 37 > RakudoPkgFedora37-2023.05.01.x86_64.rpm > https://github.com/nxadm/rakudo-pkg/releases > > The `/$0$1 $2/` is not coming out correct. > Is this a bug or

Is this a regex bug?

Hi All, Fedora 37 RakudoPkgFedora37-2023.05.01.x86_64.rpm https://github.com/nxadm/rakudo-pkg/releases The `/$0$1 $2/` is not coming out correct. Is this a bug or did I do something wrong? Many thanks, -T $ curl -L http://vpaste.net/pxRm6 -o - #!/bin/raku print "\n"; my Str $

Re: Pointer to bug question

On 11/27/22 19:13, Clifton Wood wrote: ToddAndMargo: Why are you referencing NativeHelpers::Blob when I've linked to the code you need. The bug was in the code snippet I've sent. NONE of my stuff is available via zef because CURI (and hence zef) have problems with large scale code that I am

Re: Pointer to bug question

On 11/27/22 19:13, Clifton Wood wrote: ToddAndMargo: Why are you referencing NativeHelpers::Blob when I've linked to the code you need. The bug was in the code snippet I've sent. NONE of my stuff is available via zef because CURI (and hence zef) have problems with large scale code that I am

Re: Pointer to bug question

ToddAndMargo: Why are you referencing NativeHelpers::Blob when I've linked to the code you need. The bug was in the code snippet I've sent. NONE of my stuff is available via zef because CURI (and hence zef) have problems with large scale code that I am still trying to resolve. You should be able

bug in REPL and REPL comment Was: Re: bug in REPL

of type NQPMu > > > REPL does not like the $j. This works for me when I add a couple of 'my's for $j and $k. So it seems a bug to me. Environment details follow signature. My usual plaint with the REPL is just that it is a REPL and so cannot always behave like the compiler unless it gets a

Bug in NativeCall

Fedora 36 rakudo-pkg-2022.7.0-03.x86_64 say $ppSessionInf.deref.WHAT; Internal error: unhandled target type

bug in REPL

Fedora 36 rakudo-pkg-2022.7.0-03.x86_64 > use NativeCall > $j =6; $k = CArray[uint8].new(0xFF xx $j ); print $j ~ "\n"; Cannot find method 'qast' on object of type NQPMu REPL does not like the $j.

Re: Pointer to bug question

On 11/23/22 20:01, Clifton Wood wrote: Long story short: my $a = GLib::Roles::TypedBuffer[.new($ppSessionInf); $a.setSize($pCount, :forced); my @sessions = $a.Array; That should return you an array of objects. raku PopUpTest2.pl6 ===SORRY!=== Error while compiling

Re: Pointer to bug question

@ToddAndMargo I'm about to go to sleep for the night. I thought I sent you a link to a role that someone gave me for solving this problem. Please check out this role . Please feel free to download the entire file

Re: Pointer to bug question

Hi All, This is driving me nuts! Native Call question. I have a Pointer ($ppSessionInf). It points to a structure of $pCount bytes. How do I load what $ppSessionInf points to into $Sessions # something gets assigned to it from an API call

Re: Pointer to bug question

On 11/23/22 18:21, Clifton Wood wrote: What type is BYTE, pray tell? constant BYTE := uint8; -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~

Re: Pointer to bug question

On 11/23/22 18:07, ToddAndMargo via perl6-users wrote: removing my typos: Hi All, This is driving me nuts! Native Call question. I have a Pointer ($ppSessionInf). It points to a structure of $pCount bytes. How do I load what $ppSessionInf points to into $Sessions    # something gets

Re: Pointer to bug question

@ToddAndMargo -- Also, Pointer cannot deref a Pointer, which I think is the real error. On Wed, Nov 23, 2022 at 9:21 PM Clifton Wood wrote: > @ToddAndMargo - Did you try my suggestion with > GLib::Roles::TypedBuffer? > > The "unhandled target type" occurs when NativeCall can't figure out how

Re: Pointer to bug question

@ToddAndMargo - Did you try my suggestion with GLib::Roles::TypedBuffer? The "unhandled target type" occurs when NativeCall can't figure out how to deref the referenced value. In this case, this would be the BYTE of the CArray. What type is BYTE, pray tell? - Cliff On Wed, Nov 23, 2022 at

Re: Pointer to bug question

removing my typos: Hi All, This is driving me nuts! Native Call question. I have a Pointer ($ppSessionInf). It points to a structure of $pCount bytes. How do I load what $ppSessionInf points to into $Sessions # something gets assigned to it from an API call my Pointer $ppSessionInf =

Pointer to bug question

Hi All, This is driving me nuts! Native Call question. I have a Pointer ($ppSessionInf). It points to a structure of $pCount bytes. How do I read that into a Buf of $ my DWORD $pCount = 0; bytes? my Pointer $ppSessionInf = Pointer.new(); my DWORD $pCount = 32 times

Re: append to Bug question

Typo. Should have been: append to Buf question And in my Keeper, I keep typing "bugger" instead of "buffer". Can't win.

Re: append to Bug question

On 6/18/22 22:58, Bruce Gray wrote: If all you want is to append 0xBB to $y, either of these will work: $y ~= Buf.new(0xBB); $y.append(0xBB); Did not realize I could use buf new like that. Thank you! Append numbers to a buffer: > $x Buf:0x<41 42 43 44> > $x.append( 0xDD );

Re: append to Bug question

On 6/18/22 22:58, Bruce Gray wrote: From just looking at your code, I am not clear on what you are trying to do. I am updating my Keeper on buffers. I have four of them that are a mess and I an going to consolidate them into a single .ODT (open document text) file with an index.

Re: append to Bug question

> On Jun 18, 2022, at 11:13 PM, ToddAndMargo via perl6-users > wrote: > > Hi All, > > What am I doing wrong here: From just looking at your code, I am not clear on what you are trying to do. > > my Buf $y = Buf.new( 0xFA xx 10); > Buf:0x > > > $y ~= 0xBB.encode.Buf; > Buf:0x > > I got

Re: append to Bug question

On 6/18/22 21:13, ToddAndMargo via perl6-users wrote: Hi All, What am I doing wrong here: > my Buf $y = Buf.new( 0xFA xx 10); Buf:0x > $y ~= 0xBB.encode.Buf; Buf:0x I got three entries (31 38 37) instead of one (0xBB) Some more goofing around: > $y ~= 0xBB; Stringification of a Buf is

Re: append to Bug question

On 6/18/22 22:12, ToddAndMargo via perl6-users wrote: What am I doing wrong here too? my $d = buf8.new( 0xDE..0xDB ); Buf[uint8]:0x<> Not sure why the above did not work, but this does: Presalt with swept entries: > my buf8 $e = buf8.new(0x5..0x8); Buf[uint8]:0x<05 06 07 08> > my

Re: append to Bug question

What am I doing wrong here too? my $d = buf8.new( 0xDE..0xDB ); Buf[uint8]:0x<> -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~

append to Bug question

Hi All, What am I doing wrong here: > my Buf $y = Buf.new( 0xFA xx 10); Buf:0x > $y ~= 0xBB.encode.Buf; Buf:0x I got three entries (31 38 37) instead of one (0xBB) Some more goofing around: > $y ~= 0xBB; Stringification of a Buf is not done with 'Str'. The 'decode' method should be used

Re: probably worth a bug report ?

b xxx ( Pair $test ) { $test.raku.say } > xxx key => 'value'; > > and i think it's worth a bug: i don't know if > > xxx key => 'value' > > should parse but at least it deserve a less > confusing message, don't you think ? > > regards > marc

Re: probably worth a bug report ?

Le Sun, Jan 02, 2022 at 12:32:46PM +0100, Elizabeth Mattijsen a écrit : > Maybe first explain why the error thanks for the explaination. especially > $ raku -e 'sub a(|c) { dd c }; a b => 42' > \(:b(42)) now my sub works the way I wanted: sub got (|c) { for c.hash.kv -> $rule

Re: probably worth a bug report ?

on MoarVM version 2021.09. > > by running this: > > <<\-. raku; raku -v > sub xxx ( Pair $test ) { $test.raku.say } > xxx key => 'value'; > > and i think it's worth a bug: i don't know if > > xxx key => 'value' > > should parse but at least it deserve a less > confusing message, don't you think ? > > regards > marc

probably worth a bug report ?

on MoarVM version 2021.09. by running this: <<\-. raku; raku -v sub xxx ( Pair $test ) { $test.raku.say } xxx key => 'value'; and i think it's worth a bug: i don't know if xxx key => 'value' should parse but at least it deserve a less confusing message, don

Re: Nested `whenever` (was Re: Help with bug)

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

Re: Nested `whenever` (was Re: Help with bug)

À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

Nested `whenever` (was Re: Help with bug)

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,

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: 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: Help with bug

On Tue, Dec 29, 2020 at 17:16 Elizabeth Mattijsen wrote: > Using an `await` inside a react, feels like a code smell to me. An > `await` will I suggest using 'note' for debugging instead of print or say so info is not delayed and goes straight to stderr. -Tom

Re: Help with bug

, it looks like it most commonly hangs this > way: > > * client sends ``SENDING`` > * server reads it, sends the 340 > * the client does *not* see a new line from the connection > > But, if I replace ``IO::Socket::Async::SSL`` with plain > ``IO::Socket::Async``, I can't ma

Re: Help with bug

Às 19:12 de 29/12/20, Gianni Ceccarelli escreveu: I fear we've uncovered a hard-to-diagnose bug in ``IO::Socket::Async::SSL`` … :-( Thanks for the confirmation. Hopefully this can be used as a test case to help solve it. Best regards, David Santiago

Re: Help with bug

ient does *not* see a new line from the connection But, if I replace ``IO::Socket::Async::SSL`` with plain ``IO::Socket::Async``, I can't make it hang anymore. I fear we've uncovered a hard-to-diagnose bug in ``IO::Socket::Async::SSL`` … -- dakkar - GPG public key fingerprint =

Re: Help with bug

Hi! Gianni Ceccarelli wrote: if $line ~~ /^340/ { await $conn.print("[$consumer]: value $val\r\n"); } else { done; } Notice that if the client receives a 340, it sends stuff back to the server, and *does not exit*. You may want to add a ``done`` after that

Re: Help with bug

On 2020-12-29 David Santiago wrote: > I need some help in debugging my script. Sometimes it hangs and i > don't know why. I'm pretty sure it hangs in the inner ``react``:: if $line ~~ /^340/ { await $conn.print("[$consumer]: value $val\r\n"); } else { done; } Notice

Re: Help with bug

On 12/29/20 4:37 AM, David Santiago wrote: Hi! I need some help in debugging my script. Sometimes it hangs and i don't know why. Hi David, I do not know if it will help you, but in my longer programs I have found that "say" will print out the prior valuies of things and generally drove me

Help with bug

Hi! I need some help in debugging my script. Sometimes it hangs and i don't know why. There's a channel with all the values, and then i create N promises to take a value from the channel and to write it to a socket. (one producer with multiple consumers) I'm attaching two scripts

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

If the issue is that you aren’t comfortable enough with Git¹, I assume as part of the basic toolkit of a sysadmin you know how to generate a unified diff patchfile (with `diff -ruN` or equivalent)? If so, if you generate one and upload it attached to a GitHub issue, we can figure out how to turn

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-17 11:55, Tom Browder wrote: On Fri, Jan 17, 2020 at 1:44 PM ToddAndMargo via perl6-users wrote: ... Was this what you were referring to? https://github.com/Raku/doc/blob/master/CONTRIBUTING.md No, check this link:

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On Fri, Jan 17, 2020 at 1:44 PM ToddAndMargo via perl6-users wrote: ... > Was this what you were referring to? > > https://github.com/Raku/doc/blob/master/CONTRIBUTING.md No, check this link: https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-17 11:43, ToddAndMargo via perl6-users wrote: On 2020-01-17 06:58, Tom Browder wrote: On Fri, Jan 17, 2020 at 06:06 Todd Chester via perl6-users mailto:perl6-us...@perl.org>> wrote:     On 2020-01-17 00:12, Veesh Goldman wrote: > he's finally looked into making pull

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-17 06:58, Tom Browder wrote: On Fri, Jan 17, 2020 at 06:06 Todd Chester via perl6-users mailto:perl6-us...@perl.org>> wrote: On 2020-01-17 00:12, Veesh Goldman wrote: > he's finally looked into making pull requests. Do you have a link to the pull requests for the

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-17 06:15, Shlomi Fish wrote: Hi Todd, On Fri, 17 Jan 2020 04:06:10 -0800 Todd Chester via perl6-users wrote: On 2020-01-17 00:12, Veesh Goldman wrote: he's finally looked into making pull requests. Do you have a link to the pull requests for the documentation? I'd like to add

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On Fri, Jan 17, 2020 at 06:06 Todd Chester via perl6-users < perl6-us...@perl.org> wrote: > > > On 2020-01-17 00:12, Veesh Goldman wrote: > > he's finally looked into making pull requests. > > Do you have a link to the pull requests for > the documentation? I'd like to add some examples > to a

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

Hi Todd, On Fri, 17 Jan 2020 04:06:10 -0800 Todd Chester via perl6-users wrote: > On 2020-01-17 00:12, Veesh Goldman wrote: > > he's finally looked into making pull requests. > > Do you have a link to the pull requests for > the documentation? I'd like to add some examples > to a few pages.

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-17 00:12, Veesh Goldman wrote: he's finally looked into making pull requests. Do you have a link to the pull requests for the documentation? I'd like to add some examples to a few pages.

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

I just want to point out in Todd's credit that he both admitted that he doesn't know how to use github, and that he's finally looked into making pull requests. On Fri, Jan 17, 2020 at 1:21 AM Elizabeth Mattijsen wrote: > > On 16 Jan 2020, at 21:13, ToddAndMargo via perl6-users < >

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

> On 16 Jan 2020, at 21:13, ToddAndMargo via perl6-users > wrote: > On 2020-01-16 12:09, Elizabeth Mattijsen wrote: >>> On 16 Jan 2020, at 20:29, Darren Duncan wrote: >>> On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote: I wonder if this is how you treat your family as well. If you do,

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

Trey, I am wrong ALL THE TIME. I have to apologize all the time too. I live with egg on my face constantly. You get use to it. When I am in the wrong, I will bend over five way to Sunday to apologize. If you decide to take offense where none is intended and you have it explained to

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On Thu, Jan 16, 2020 at 15:04 ToddAndMargo via perl6-users < perl6-us...@perl.org> wrote: > On 2020-01-16 11:00, Trey Harris wrote: > and your apparent misapprehension that > merely explaining away a statement that some took offense to, without > any outward sign of contrition, inoculates you

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-16 12:09, Elizabeth Mattijsen wrote: On 16 Jan 2020, at 20:29, Darren Duncan wrote: On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote: I wonder if this is how you treat your family as well. If you do, then I feel sorry for your family. And wouldn't be surprised if they abandoned

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-16 12:09, ToddAndMargo via perl6-users wrote: On 2020-01-16 11:29, Darren Duncan wrote: On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote: I wonder if this is how you treat your family as well.  If you do, then I feel sorry for your family.  And wouldn't be surprised if they

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

> On 16 Jan 2020, at 20:29, Darren Duncan wrote: > On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote: >> I wonder if this is how you treat your family as well. If you do, then I >> feel sorry for your family. And wouldn't be surprised if they abandoned you. > That is unnecessarily harsh and

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-16 11:29, Darren Duncan wrote: On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote: I wonder if this is how you treat your family as well.  If you do, then I feel sorry for your family.  And wouldn't be surprised if they abandoned you. That is unnecessarily harsh and uncalled for

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-16 11:00, Trey Harris wrote: On Thu, Jan 16, 2020 at 12:19 ToddAndMargo via perl6-users mailto:perl6-us...@perl.org>> wrote: As far as the Dog remark, I have told you and others ENDLESSLY what that meant.  That you continue to deliberately misrepresent me on this is a

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote: I wonder if this is how you treat your family as well. If you do, then I feel sorry for your family. And wouldn't be surprised if they abandoned you. That is unnecessarily harsh and uncalled for Liz, the last sentence particularly. --

Re: Bug to report: cardinal called an integer

On 2020-01-16 9:22 a.m., ToddAndMargo via perl6-users wrote: Since folks do not like the programming/math term "carinal", it would be perfectly happy if the error message was changed from: This type cannot unbox to a native integer: P6opaque, Str to This type cannot unbox to a native unsigned

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On Thu, Jan 16, 2020 at 12:19 ToddAndMargo via perl6-users < perl6-us...@perl.org> wrote: > As far as the Dog remark, I have told you and others > ENDLESSLY what that meant. That you continue to > deliberately misrepresent me on this is a moral > issue on your part. The issue is not, now, just

Re: Bug to report: cardinal called an integer

On 2020-01-09 10:10, ToddAndMargo via perl6-users wrote: Hi All, A bug to report: $ perl6 -v This is Rakudo version 2019.07.1 built on MoarVM version 2019.07.1 implementing Perl 6.d. $ p6 'my uint32 $c; $c = "ABC";' This type cannot unbox to a native integer: P6opaque, Str   in bl

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

Hi Liz, The Pull Request seems a much better route than the bug reporter. I went to the bug reporter as I am familiar with such from Fedora and others where you can ask for enhancements, etc. on the bug reporter. As far as the Dog remark, I have told you and others ENDLESSLY what that meant

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

> On 16 Jan 2020, at 02:24, ToddAndMargo via perl6-users > wrote: > Programming is only part of my business. I am a > consultant to small business. I do EVERYTHING, although > I draw the line at stringing wire. Fortunately, I have > guys that will string wire for me. Apparently you also draw

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-15 17:32, Tillman Peng wrote: I in fact like to read Todd's every post. Because of his active posting, I know perl6 is there and still alive. regards. Thank you for that. :-)

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

tring literal. in C! In WinAPI, calls Your holding on to NOT-A-BUG It is not a bug! By definition. The way C handles strings is not the way Raku handles strings. Raku handles strings in a clearly defined manner and it adheres to those definitions. No bug in Raku. Perhaps if you were

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-15 16:59, Peter Scott wrote: On 1/15/2020 2:39 PM, ToddAndMargo via perl6-users wrote: On 2020-01-15 14:18, Elizabeth Mattijsen wrote: Thank you Richard for this long and thoughtful answer. I have already given up on Todd, I'm glad to see others haven't (yet).  What will follow is

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

what I find to the bug reported, but I can't get past my good e-friend JJ, so I gave up. I can't even get him to fix the C String error. So I post them here. JJ actually took the one about the missing graphic. Kind of surprised me. Had I posted it to the bug reported, I believe it would have bee

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 1/15/2020 2:39 PM, ToddAndMargo via perl6-users wrote: On 2020-01-15 14:18, Elizabeth Mattijsen wrote: Thank you Richard for this long and thoughtful answer. I have already given up on Todd, I'm glad to see others haven't (yet).  What will follow is probably a response that is either: a.

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-15 15:36, Trey Harris wrote: And there’s another example of exactly the sort of things Richard brought up. How about: “I feel like Richard has not liked me for a long time, and that there’s nothing I can do about it. I feel like I could say almost anything and he would find

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On Wed, Jan 15, 2020 at 18:38 ToddAndMargo via perl6-users < perl6-us...@perl.org> wrote: > On 2020-01-15 15:50, Laurent Rosenfeld via perl6-users wrote: > > So, the way you behave with him is just nasty and evil. Please stop > > doing that. > > That is in your own head. Todd, why can't you

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-15 15:50, Laurent Rosenfeld via perl6-users wrote: So, the way you behave with him is just nasty and evil. Please stop doing that. That is in your own head.

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

The point is really not whether people like you or don't, and also not about whether you like specific people or don't. I don't know you (at least personally), you don't know me personally, and nobody cares about whether I like you or whether you like me. The whole point is about being polite,

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-15 15:36, Trey Harris wrote: artificially-hyperbolized reference to JJ helped anything after previously calling him a dog. To anyone still misunderstanding this. "Guard Dog" is a figure of speech. It means he is over protective. I DID NOT CALL HIM A DOG. And JJ knew this. I was

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On Wed, Jan 15, 2020 at 17:39 ToddAndMargo via perl6-users < perl6-us...@perl.org> wrote: > On 2020-01-15 14:18, Elizabeth Mattijsen wrote: > > Thank you Richard for this long and thoughtful answer. > > > > I have already given up on Todd, I'm glad to see others haven't (yet). > What will follow

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-15 15:05, Laurent Rosenfeld via perl6-users wrote: I join with Liz and Tom to thank you, Richard, for this long and thoughtful answer. Hi Laurent, I can be long winded too. Wait, it is okay for Richard, but not for me? Anyway, I will eventually wear you down and we will become

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

Richard, Please put aside your personal distaste of me when writing on this group. Write me off line if you want to want to vent. -T

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-15 14:25, Tom Browder wrote: On Wed, Jan 15, 2020 at 4:19 PM Elizabeth Mattijsen wrote: Thank you Richard for this long and thoughtful answer. Amen, Liz! -Tom (tbrowder) With love and understanding, I will wear both you down and we will become friends again.

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

  And with a string literal, you have to also keep track of the length of the string literal. in C! In WinAPI, calls Your holding on to NOT-A-BUG It is not a bug! By definition. The way C handles strings is not the way Raku handles strings. Damned tootin' it is a bug. If you can not properl

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

Todd, You just did exactly what Liz said you would do by writing 'Richard has not liked me for a long time'. Do you not even re-read your own posts or have the self-awareness to recognise it? Really? Does it matter whether or not 'I like you'? This list is not some place for social media

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

umentation makes a distinction between a String and a > String literal and so ...". > > > They are two different things. > > In C! We are discussing Raku documentation where strings are objects, > and can contain zero or more characters and characters that conform to >

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On 2020-01-15 14:18, Elizabeth Mattijsen wrote: Thank you Richard for this long and thoughtful answer. I have already given up on Todd, I'm glad to see others haven't (yet). What will follow is probably a response that is either: a. everybody is against me, b. the Raku community won't

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

On Wed, Jan 15, 2020 at 4:19 PM Elizabeth Mattijsen wrote: > > Thank you Richard for this long and thoughtful answer. Amen, Liz! -Tom (tbrowder)

Re: Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

a distinction between a String and a > String literal and so ...". > >> They are two different things. > > In C! We are discussing Raku documentation where strings are objects, and can > contain zero or more characters and characters that conform to Unicode. >

Once again - You say one thing and do another Re: Bug to report: cardinal called an integer

e nuls in them that are part of the string literal.  And with a string literal, you have to also keep track of the length of the string literal. in C! In WinAPI, calls Your holding on to NOT-A-BUG It is not a bug! By definition. The way C handles strings is not the way Raku handles st

Re: Bug to report: cardinal called an integer

On 2020-01-13 23:11, Darren Duncan wrote: Yes, a uint32 CAN represent a cardinal, but it can ALSO represent an ordinal or a nominal or various other things. It would help me if you would show me some examples of a uint would values were not whole nubmers greater than or equal to zero $_

  1   2   3   4   5   6   7   8   9   10   >