A while ago, I asked the question Reconstructing an (SV *) when you know the address and the precise structure of the said SV.
As it turns out, this approach fails for the purpose of application (IPC::Door) that I sought the advice for, due to the (apparent) limitation of the library involved. (Documentation does not mention such limitation, however.) The library works, passing back and forth a pointer to a simple C data types such as int or char(I have not tested all C data types). And struct works, too, as long as struct itself contains no other pointers.
So, instead of the usual SV* , I need int* or char* or something like that to pass around. Obviously, one might consider Data::Dumper-esque approach of flattening data to an ASCII string and pass that around, but obviously this is an increasingly costly solution for larger data structures. If you have any suggestion on how to efficiently "flatten" perl's internal data, I'd appreciate it. I am not a very experienced C programmer, but I'd do my best to understand your suggestions! :)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
