On Mon, Jan 6, 2020, 09:01 ToddAndMargo via perl6-users
mailto:perl6-us...@perl.org>> wrote:
On 2020-01-05 22:56, ToddAndMargo via perl6-users wrote:
> do they rise to the level of actually helping others?
I am afraid I am annoying more than helping
On 2020-01-05 23:20, Veesh Go
This sort of thing should be in one repo, because it's one now project.
And GitHub is non-intrusive, so it can't possibly annoy anyone.
On Mon, Jan 6, 2020, 09:01 ToddAndMargo via perl6-users <
perl6-us...@perl.org> wrote:
> On 2020-01-05 22:56, ToddAndMargo via perl6-users wrote:
> > do they ri
On 2020-01-05 22:56, ToddAndMargo via perl6-users wrote:
do they rise to the level of actually helping others?
I am afraid I am annoying more than helping
On 2020-01-05 22:12, Veesh Goldman wrote:
You can keep all of them on GitHub. It would make it easy to download
and run your code samples, and to collaborate.
That sounds like a good idea. Each in a separate project?
Also, do they rise to the level of actually helping others?
You can keep all of them on GitHub. It would make it easy to download and
run your code samples, and to collaborate.
On Mon, Jan 6, 2020, 03:26 ToddAndMargo via perl6-users <
perl6-us...@perl.org> wrote:
> Hi All,
>
> My new Keeper on NativeCall and Win API calls
> is getting close to ready. Un
Hi All,
My new Keeper on NativeCall and Win API calls
is getting close to ready. Unfortunately, it
is up to 301 lines now. That would make for
a hassle for those reading on cell phones as
well a swamp the group.
Where would be a good place to publish it? I
specifically want to target this lis
On 2019-12-29 17:05, ToddAndMargo via perl6-users wrote:
Native Call is tack the chr(0) at the end for you, most of the time
Mistake on my part. No it won't. You have to add it yourself.
On 2019-12-29 14:56, ToddAndMargo via perl6-users wrote:
Hi All,
This is my keeper on Native Call.
-T
Raku: Native Call notes:
Really poor reference: https://docs.raku.org/language/nativecall
1) Kernel32.dll call variables with a "p" in them are "C" pointers.
LSTATUS RegOpenKeyExW(
Hi All,
This is my keeper on Native Call.
-T
Raku: Native Call notes:
Really poor reference: https://docs.raku.org/language/nativecall
1) Kernel32.dll call variables with a "p" in them are "C" pointers.
LSTATUS RegOpenKeyExW(
HKEYhKey,
LPCWSTR lpSubKey,
DWORD
