On 2020-01-01 11:11, JJ Merelo wrote:
It will not be corrected because it's not a documentation error.
Exactly. And it is an error because it does not
conform to "C" standards for strings. That you
got some examples to work is just dumb luck. I
had no such dumb luck.
Also,
using strings in the way your other (native) libraries need is just
common sense, that goes without saying, or "is left as an exercise to
the student".
You presume "C" programming knowledge from Raku programmers.
I have to ask over on the "C" group a lot. They have been
very helpful. They think I am a bit weird (I am) but help
me anyway.
So "is left as an exercise to the student" means the student
should first take a course in "C" programming to get around
all the goofs and oversights in the documentation?
The documentation, should show actual "C" calls to various WinAPI with
their "C" definitions and how to write them
with NativeCall, but does not. What we have now wonderful
documentation that is useless and won't get fixed.
In general, you don't need to null-terminate strings, and
that's what the example goes.
Really. That is not the way "C" works. In those
example pictures I ran, I had to run them several
time to get them to careen. It all depends
on what garbage "C" find outside your string.
Any wrapper to a native library which
_does_ need that should specifically say so.
If it is talking "C", it certainly always does.
NativeCall has no excuse for ignoring how "C"
actually works.
Yours,
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
