Re: stolen uint's

On 2020-01-30 17:20, Veesh Goldman wrote: Hi Todd, A couple of things. One is that Int and int are totally unrelated concepts. Captial Int is a high level concept, which has a type constraint related to it, and belongs to raku's object system. Lowercase int is a special case, it's only for

Re: stolen uint's

Hi Todd, A couple of things. One is that Int and int are totally unrelated concepts. Captial Int is a high level concept, which has a type constraint related to it, and belongs to raku's object system. Lowercase int is a special case, it's only for the interface with C, and it represents a low

Re: stolen uint's

On 2020-01-30 08:11, Andy Bach wrote: I’m STILL waiting for you to show me ONE example of a `uint` turning into `int`. Not `Int`, via auto-boxing, `int`, via who-knows-what. $ p6 'my uint8 $u; say $u.^name;' Int Did you not notice the capital "I" in both his request and your code output?

Re: stolen uint's

On 2020-01-29 17:45, Trey Harris wrote: On Wed, Jan 29, 2020 at 20:20 ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: On 2020-01-29 10:28, Trey Harris wrote: > B is not a subset of A. That is the relationship of uint and int—two > distinct types whose values

Re: stolen uint's

On Wed, Jan 29, 2020 at 20:20 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-29 10:28, Trey Harris wrote: > > B is not a subset of A. That is the relationship of uint and int—two > > distinct types whose values happen to overlap in a way that describes a > > subset. Perl

Re: stolen uint's

On 2020-01-29 10:28, Trey Harris wrote: B is not a subset of A. That is the relationship of uint and int—two distinct types whose values happen to overlap in a way that describes a subset. Perl isn’t Prolog; a logical relationship between two types is not a first-class entity of the language.

Re: stolen uint's

On 2020-01-28 18:50, ToddAndMargo via perl6-users wrote: This all came up when I tried to match   RegSetValueExW( _In_ HKEY hKey, _In_opt_ LPCWSTR lpValueName, _Reserved_ DWORD Reserved, _In_ DWORD dwType, _In_reads_bytes_opt_(cbData) CONST BYTE * lpData, _In_ DWORD cbData where CbData 

Re: stolen uint's

On 2020-01-29 16:00, Trey Harris wrote: where CbData can either be a UTF little endian C string, I understand now. I typo'ed cbData. That should have been lpData. :'(

Re: stolen uint's

On Wed, Jan 29, 2020 at 18:39 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-29 15:32, ToddAndMargo via perl6-users wrote: > > `DWORD cbData` > > cbData is a 32 bit unsigned integer. It follows > all the rules for unsigned integers. You do not > terminate it. WinAPI

Re: stolen uint's

On 2020-01-29 15:32, ToddAndMargo via perl6-users wrote: `DWORD cbData` cbData is a 32 bit unsigned integer. It follows all the rules for unsigned integers. You do not terminate it. WinAPI knows it is 32 bits long. lpData (Long Pointer Data) is where you put the 0x at the end, if you

Re: stolen uint's

On 2020-01-29 15:22, Trey Harris wrote: On Wed, Jan 29, 2020 at 17:52 ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: On 2020-01-29 14:20, Trey Harris wrote: > I don’t care about IpData or ValueData—those are completely unremarkable > fields. Showing me

Re: stolen uint's

On Wed, Jan 29, 2020 at 17:52 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-29 14:20, Trey Harris wrote: > > I don’t care about IpData or ValueData—those are completely unremarkable > > fields. Showing me more code relating to them—or any other fields > > besides

Re: stolen uint's

On 2020-01-29 14:20, Trey Harris wrote: I don’t care about IpData or ValueData—those are completely unremarkable fields. Showing me more code relating to them—or any other fields besides cData—isn’t helpful to understanding how the 3-bytes UTF + null cData field works. hi Trey, I think what

Re: stolen uint's

I’m still asking you the same question I asked in https://www.nntp.perl.org/group/perl.perl6.users/2020/01/msg8029.html I don’t care about IpData or ValueData—those are completely unremarkable fields. Showing me more code relating to them—or any other fields besides cData—isn’t helpful to

Re: stolen uint's

Widows Chuckle. You should see how I typo `shutdown`. The "i" and the "u" are a little too close to each other. -- ~~ When you say, "I wrote a program that crashed Windows," people just stare at you blankly and say, "Hey, I got those with the system, for

Re: stolen uint's

On 2020-01-29 13:01, Trey Harris wrote: On Wed, Jan 29, 2020 at 15:28 ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: "Todd" would convert to      84 00 111 00 100 00 100 00 00 00 I’m sorry, you misunderstood me. I wasn’t asking how to convert text into UTF. I

Re: stolen uint's

On Wed, Jan 29, 2020 at 15:28 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > "Todd" would convert to > 84 00 111 00 100 00 100 00 00 00 I’m sorry, you misunderstood me. I wasn’t asking how to convert text into UTF. I was asking for an example of the 3-byte UTF plus 32-bit

Re: stolen uint's

On 2020-01-29 11:36, Trey Harris wrote: On Wed, Jan 29, 2020 at 14:01 ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: On 2020-01-29 06:34, Trey Harris wrote: > I was going to ask about that (but it seemed out of Raku-world, and I > don’t even play someone

Re: stolen uint's

On Wed, Jan 29, 2020 at 14:39 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-29 11:32, Trey Harris wrote: > > On Wed, Jan 29, 2020 at 13:50 ToddAndMargo via perl6-users > > mailto:perl6-users@perl.org>> wrote: > > > > Why don't use use > > > >

Re: stolen uint's

On 2020-01-29 11:32, Trey Harris wrote: On Wed, Jan 29, 2020 at 13:50 ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: Why don't use use typeMappings[type_index( typeid(char) )] = "char"; Finally, a definition I can work with... We can treat this as a request for

Re: stolen uint's

On Wed, Jan 29, 2020 at 14:01 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-29 06:34, Trey Harris wrote: > > I was going to ask about that (but it seemed out of Raku-world, and I > > don’t even play someone who knows about Windows on TV), but, okay, I’ll > > bite...

Re: stolen uint's

On 2020-01-29 11:17, William Michels via perl6-users wrote: "I am not posting it here as it is several hundred lines long and then I'd get the finger wagged at me. Everything is spread across several modules." On the contrary, this email list is the perfect place to put up nascent Raku/Perl6

Re: stolen uint's

On Wed, Jan 29, 2020 at 13:50 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > Why don't use use > > typeMappings[type_index( typeid(char) )] = "char"; > Finally, a definition I can work with... We can treat this as a request for typeid(); the mapping creation and lookup is an

Re: stolen uint's

> "I am not posting it here as it is several hundred lines long and then I'd > get the finger wagged at me. Everything is spread across several modules." On the contrary, this email list is the perfect place to put up nascent Raku/Perl6 that you're having problems with. The issue is you making

Re: stolen uint's

On 2020-01-29 10:58, Tom Browder wrote: On Wed, Jan 29, 2020 at 12:34 PM ToddAndMargo via perl6-users wrote: On 2020-01-29 00:43, Tobias Boege wrote: On Tue, 28 Jan 2020, ToddAndMargo via perl6-users wrote: This all came up when I tried to match ... if $ValueData.^name ne "Int" ||

Re: stolen uint's

On 2020-01-29 06:34, Trey Harris wrote: I was going to ask about that (but it seemed out of Raku-world, and I don’t even play someone who knows about Windows on TV), but, okay, I’ll bite... what are some examples of the precisely 3-byte + 32-bit null UTF strings you imagine being encoded by

Re: stolen uint's

On Wed, Jan 29, 2020 at 12:34 PM ToddAndMargo via perl6-users wrote: > On 2020-01-29 00:43, Tobias Boege wrote: > > On Tue, 28 Jan 2020, ToddAndMargo via perl6-users wrote: > >> This all came up when I tried to match ... > if $ValueData.^name ne "Int" || $ValueData < 0 { # UInt gets >

Re: stolen uint's

On 2020-01-28 17:00, Trey Harris wrote: On Tue, Jan 28, 2020 at 19:58 ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: On 2020-01-28 16:56, Trey Harris wrote: > In other words—yes, you want Raku to attempt to provoke a segmentation > fault, then recover and

Re: stolen uint's

On 2020-01-29 00:43, Tobias Boege wrote: On Tue, 28 Jan 2020, ToddAndMargo via perl6-users wrote: This all came up when I tried to match RegSetValueExW( _In_ HKEY hKey, _In_opt_ LPCWSTR lpValueName, _Reserved_ DWORD Reserved, _In_ DWORD

Re: stolen uint's

On Wed, Jan 29, 2020 at 13:28 Trey Harris wrote: > whose values happen to overlap in a way that describes a subset. Perl > isn’t Prolog; > It isn’t either, but that’s irrelevant; I meant Raku obviously. Thinko. >

Re: stolen uint's

On Wed, Jan 29, 2020 at 13:04 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-29 09:19, Trey Harris wrote: > > > > The first line of https://docs.raku.org/type/UInt is: > > > The `|Int`| is defined as a subset of `|Int|:` > > > > How does that not “reflect that UInt is

Re: stolen uint's

On 2020-01-29 09:19, Trey Harris wrote: The first line of https://docs.raku.org/type/UInt is: > The `|Int`| is defined as a subset of `|Int|:` How does that not “reflect that UInt is not a unique [type, I assume you meant], but a subset of Int”? You are correct. Mumble, mumble.

Re: stolen uint's

On 2020-01-29 09:20, Trey Harris wrote: Argh! Editing error... On Wed, Jan 29, 2020 at 12:19 Trey Harris > wrote: The first line of https://docs.raku.org/type/UInt is: > The `|Int`| is defined as a subset of `|Int|:` Should have been (and is in that URL)

Re: stolen uint's

Argh! Editing error... On Wed, Jan 29, 2020 at 12:19 Trey Harris wrote: > The first line of https://docs.raku.org/type/UInt is: >> > > The `Int` is defined as a subset of `Int:` > Should have been (and is in that URL) “The `UInt` is defined as…”

Re: stolen uint's

On Wed, Jan 29, 2020 at 11:58 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-28 22:16, Veesh Goldman wrote: > > Hi Todd, > > I'd just like to point out one thing. Your confusion here (and in a few > > related posts) is that you aren't grokking the difference between uint

Re: stolen uint's

On 2020-01-28 22:16, Veesh Goldman wrote: Hi Todd, I'd just like to point out one thing. Your confusion here (and in a few related posts) is that you aren't grokking the difference between uint and UInt. Hi Veesh, I am well aware of the difference between UInt and uint. Two weeks ago I was

Re: stolen uint's

On Wed, Jan 29, 2020 at 03:44 Tobias Boege wrote: > On Tue, 28 Jan 2020, ToddAndMargo via perl6-users wrote: > > This all came up when I tried to match > > > > RegSetValueExW( > > _In_ HKEY hKey, > > _In_opt_ LPCWSTR lpValueName, > > _Reserved_ DWORD Reserved,

Re: stolen uint's

On Tue, 28 Jan 2020, ToddAndMargo via perl6-users wrote: > This all came up when I tried to match > > RegSetValueExW( > _In_ HKEY hKey, > _In_opt_ LPCWSTR lpValueName, > _Reserved_ DWORD Reserved, > _In_ DWORD dwType, >

Re: stolen uint's

Hi Todd, I'd just like to point out one thing. Your confusion here (and in a few related posts) is that you aren't grokking the difference between uint and UInt. Please correct me if I'm wrong. But if there needs to be an update to docs, it probably should be to a document that clarifies the

Re: stolen uint's

On 2020-01-28 18:57, Trey Harris wrote: For doing that sort of thing, learning a little glue C would probably be very useful (IMO, every systems-oriented programmer is helped immensely by knowing enough C to be able to munge low-level data structures). This is a lovely little example of a

Re: stolen uint's

On Tue, Jan 28, 2020 at 22:03 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > Hi Trey, > > Any chance of you sneaking in on the doc pages > for ^name and range to explain the things you > explained to me? For `.^name`—I suppose, though I’m not sure what would be appropriate

Re: stolen uint's

On 2020-01-28 18:57, Trey Harris wrote: For doing that sort of thing, learning a little glue C would probably be very useful (IMO, every systems-oriented programmer is helped immensely by knowing enough C to be able to munge low-level data structures). This is a lovely little example of a

Re: stolen uint's

Hi Trey, Any chance of you sneaking in on the doc pages for ^name and range to explain the things you explained to me? I am a little odd in that I actually try to use the manual pages. But there may be other out there too. (Because I do not like the way the manual pages are written, does not

Re: stolen uint's

For doing that sort of thing, learning a little glue C would probably be very useful (IMO, every systems-oriented programmer is helped immensely by knowing enough C to be able to munge low-level data structures). This is a lovely little example of a numeric library using native arithmetic where

Re: stolen uint's

Question: in those instance where I ONLY want to play with 8,16, or 32 BITS and have Raku leave whatever pattern I put in them along, what is the best thing to declare them as?

Re: stolen uint's

On 2020-01-28 18:41, Trey Harris wrote: On Tue, Jan 28, 2020 at 21:18 Trey Harris > wrote: Nope. If I give you: 0x41 and tell you that’s a single octet, and that’s all you have, and I and ask you whether that’s an “A” or a decimal 97 or something else

Re: stolen uint's

On 2020-01-28 18:18, Trey Harris wrote: my uint $z = -32; 224 Another misunderstanding on my part. I thought it would barf. All I really need to know is what is expected. To me I am getting wrong answers back, but as long as they are consistent answers I can deal with it: if

Re: stolen uint's

On 2020-01-28 18:34, Trey Harris wrote: And that’s another thing: you’ll notice if you define a `my uint8 $x;` it will be set to 0. No undefined, no Nil. That doesn’t happen with non-native numeric values. Huh. I thought is as nil. > my uint $x; say $x.base(2) 0

Re: stolen uint's

On Tue, Jan 28, 2020 at 21:18 Trey Harris wrote: > Nope. If I give you: > > 0x41 > > and tell you that’s a single octet, and that’s all you have, and I and ask > you whether that’s an “A” or a decimal 97 or something else described by > 0101, how do you answer? You can’t. > Sorry, editing

Re: stolen uint's

On Tue, Jan 28, 2020 at 21:18 Trey Harris wrote: > values, such as 'undefined' and 'Nil' as well as its type. > > And that’s another thing: you’ll notice if you define a `my uint8 $x;` it will be set to 0. No undefined, no Nil. That doesn’t happen with non-native numeric values. > Nope. If I

Re: stolen uint's

On Tue, Jan 28, 2020 at 20:59 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > > > Ah You got ‘int’—lowercase ‘int’, not uppercase ‘Int’?? I didn’t see > > that example and I can’t find it scrolling back. Would you repost it, > > please? That would change things (and possibly

Re: stolen uint's

Ah You got ‘int’—lowercase ‘int’, not uppercase ‘Int’?? I didn’t see that example and I can’t find it scrolling back. Would you repost it, please? That would change things (and possibly indicate a bug). > my uint $u= 0xFF44; say $u.^name Int It was upper case Int. Again, wrong answer.

Re: stolen uint's

On Tue, Jan 28, 2020 at 20:32 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-28 17:17, Trey Harris wrote: > > On Tue, Jan 28, 2020 at 20:04 ToddAndMargo via perl6-users > > mailto:perl6-users@perl.org>> wrote: > > > > On 2020-01-28 17:00, Trey Harris wrote: > >

Re: stolen uint's

On 2020-01-28 17:17, Trey Harris wrote: On Tue, Jan 28, 2020 at 20:04 ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: On 2020-01-28 17:00, Trey Harris wrote: > On Tue, Jan 28, 2020 at 19:58 ToddAndMargo via perl6-users > mailto:perl6-users@perl.org>

Re: stolen uint's

On Tue, Jan 28, 2020 at 20:04 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-28 17:00, Trey Harris wrote: > > On Tue, Jan 28, 2020 at 19:58 ToddAndMargo via perl6-users > > mailto:perl6-users@perl.org>> wrote: > > > > On 2020-01-28 16:56, Trey Harris wrote: > >

Re: stolen uint's

On 2020-01-28 17:00, Trey Harris wrote: On Tue, Jan 28, 2020 at 19:58 ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: On 2020-01-28 16:56, Trey Harris wrote: > In other words—yes, you want Raku to attempt to provoke a segmentation > fault, then recover and

Re: stolen uint's

On Tue, Jan 28, 2020 at 19:58 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-28 16:56, Trey Harris wrote: > > In other words—yes, you want Raku to attempt to provoke a segmentation > > fault, then recover and tell you whether it faulted or not. > > Huh? I just want to

Re: stolen uint's

On 2020-01-28 16:56, Trey Harris wrote: In other words—yes, you want Raku to attempt to provoke a segmentation fault, then recover and tell you whether it faulted or not. Huh? I just want to know what the variable actually is. I do not wnat to crash anything.

Re: stolen uint's

On Tue, Jan 28, 2020 at 19:55 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-28 16:52, Trey Harris wrote: > > On Tue, Jan 28, 2020 at 19:46 ToddAndMargo via perl6-users > > mailto:perl6-users@perl.org>> wrote: > > > > > my uint $u= 0xFF44; say $u.^name > > Int >

Re: stolen uint's

On 2020-01-28 16:52, Trey Harris wrote: On Tue, Jan 28, 2020 at 19:46 ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: > my uint $u= 0xFF44; say $u.^name Int Wrong answer It’s absolutely the right answer. You autoboxed it by running a method—`.^name`—on it. A

Re: stolen uint's

On Tue, Jan 28, 2020 at 19:46 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > > my uint $u= 0xFF44; say $u.^name > Int > > Wrong answer > It’s absolutely the right answer. You autoboxed it by running a method—`.^name`—on it. A uint can’t respond to `.^name`, so you can never get

Re: stolen uint's

On 2020-01-28 16:30, Trey Harris wrote: On Tue, Jan 28, 2020 at 19:06 ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: On 2020-01-28 15:37, Trey Harris wrote: > > > On Tue, Jan 28, 2020 at 18:09 ToddAndMargo via perl6-users >

Re: stolen uint's

On Tue, Jan 28, 2020 at 19:06 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-01-28 15:37, Trey Harris wrote: > > > > > > On Tue, Jan 28, 2020 at 18:09 ToddAndMargo via perl6-users > > mailto:perl6-users@perl.org>> wrote: > > > > Observer effect (physics) > >

Re: stolen uint's

On 2020-01-28 15:37, Trey Harris wrote: On Tue, Jan 28, 2020 at 18:09 ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: Observer effect (physics) https://en.wikipedia.org/wiki/Observer_effect_(physics)      In physics, the observer effect is the theory that

Re: stolen uint's

On Tue, Jan 28, 2020 at 18:09 ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > Observer effect (physics) > https://en.wikipedia.org/wiki/Observer_effect_(physics) > > In physics, the observer effect is the theory that > the mere observation of a phenomenon inevitably >

Re: stolen uint's

Observer effect (physics) https://en.wikipedia.org/wiki/Observer_effect_(physics) In physics, the observer effect is the theory that the mere observation of a phenomenon inevitably changes that phenomenon ... An especially unusual version of the observer effect occurs in quantum

Re: stolen uint's

On 2020-01-25 18:36, ToddAndMargo via perl6-users wrote: Question: how do I create a 32 bit variable that is hands off to the boxing? > my native D32 is repr('P6int') is Int is nativesize(32) is unsigned { } (D32) > my D32 $d = 0xFF44; say D32.^name; say D32.Range; D32 -Inf^..^Inf

Re: stolen uint's

On 2020-01-25 18:21, Tobias Boege wrote: On Sat, 25 Jan 2020, ToddAndMargo via perl6-users wrote: Hi All, Anyone have a workaround to my stolen uint's? constant DWORD := uint32; (uint32) subset StrOrDword where Str | DWORD; (StrOrDword) sub x( StrOrDword $item ) { * say "

Re: stolen uint's

On 2020-01-25 16:58, ToddAndMargo via perl6-users wrote: Hi All, Anyone have a workaround to my stolen uint's? > constant DWORD := uint32; (uint32) > subset StrOrDword where Str | DWORD; (StrOrDword) > sub x( StrOrDword $item ) { *   say "$item is a " ~ $item.^name;

Re: stolen uint's

On Sat, 25 Jan 2020, ToddAndMargo via perl6-users wrote: > Hi All, > > Anyone have a workaround to my stolen uint's? > > > constant DWORD := uint32; > (uint32) > > > subset StrOrDword where Str | DWORD; > (StrOrDword) > > > sub x( StrOrDword $item ) {

stolen uint's

Hi All, Anyone have a workaround to my stolen uint's? > constant DWORD := uint32; (uint32) > subset StrOrDword where Str | DWORD; (StrOrDword) > sub x( StrOrDword $item ) { * say "$item is a " ~ $item.^name; * } > x( "abc" ); abc is a Str > x