Just another Perl shrine | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Just how are you creating those buffers? If you are allocating them in pure C, then you should memory manage them in C.
A typical way of dealing with such things, is to create the buffer in the high level language, in this case Perl (but it's been done in like this in VB, too), and pass the pointer to it to C, which can fill it up. That way, there's no alloc() related madness waiting on your C code. All you have to do is prefill a scalar with a large enough string. At the worst, you can still copy the contents of the buffer over to the Perl scalar just before you finish. In VB it was customary to use an API call for that: hMemCpy() in Windows 3.1, and RtlMoveMemory for Win32 — the only kind of Windows that's still alive. But of course, the strings were never that long, so maybe that approach isn't so practical. As an aside, there are several pointer related templates available for pack/unpack, such as "P"/"p". In reply to Re: converting a C pointer to a perl reference
by bart
|
|