On Sun, Jul 11, 2004 at 10:47:26PM -0400, Federico Lucifredi wrote:
> What kind of access will the scripts have to the proper C++ variables?
> Can these be objects or have to be static ? Or is it simply madness to poke
> at data that way (my take) and the best approach is to pass a data block to
> a Perl function from C++, then retrieve the results from that same memory
> area (or another one, but still allocated by C++).
You'd have to convert any variables from C++ representations to Perl. This
could be messy. Have you tried SWIG?
> The person badgering me with this problem seems to think it is possible
> to poke at the memory space of an executable from another one (the
> standalone perl interpreter) and live happily everafter. Now, I know Perl is
> full of wonderous surprises, but unless it bends even standard Unix Kernel
> memory protection, it seems to me the best way to go is embedding.
Poking at the memory space of an executable is "not a good idea" (tm).
> Should I check out other spell books other than perlembed? As far as I know,
> that's the only way to go, but perhaps there are *other* ways to embed Perl
SWIG.
> (No Dan, don't get started on Parrot juuuust yet ;-)
-Gyepi
--
Notice the difference between what happens when a man says to himself,
I have failed three times, and what happens when he says, I am a failure.
--S. I. Hayakawa
_______________________________________________
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
