On 2020-01-01 11:49, William Michels via perl6-users wrote:
Hi Todd,
Isn't the point of the NativeCall interface to call native C code?
Hi William,
Exactly! And figuring out how to do it is killing me!
https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-formatmessagew
is going to be the death of me!
By changing that requirement, won't it be harder for "native C"
programmers to contribute to the Raku/Perl6 ecosystem?
If I am not mistaken, Raku is written in "C". The developers
should know it like the back of their hands.
That being said, maybe an experienced C programmer might consider
contributing a "NativeCall Linter" module to the Raku/Perl6 ecosystem.
Maybe some "Raku developers?
Best Regards, Bill.
P.S. Following on Richard's remarks, maybe you can place the actual
code for your modules into one or more Github repositories? And you/we
can use the mailing list for extensive discussion (beyond what people
might ordinarily consider "Github issues")?
I have not done that yet as I do not consider the quality
of my code to be of that high a level. I am still
such a beginner. But it is does sound like
where I should eventually go.
Also, these things I have posted are for what I need
to get my own job done. Beyond that, I would not
be able to keep adding features that I am not
personally using.
Tip: Arrays in C are indexed starting at 0, as opposed
to starting at 1. Be nice it that was in NativeCall's
documentation too
Have a wonderful New Year! Thank you for all the tips
and suggestions.
-T
