|
in reply to Re: Blending perl and C (two approaches)
in thread Blending perl and C (two approaches)
Better yet, perhaps you could store the byte-code, and pass *that* through an embedded interpreter? (Heck, while you're at it, encrypt the byte-code as well!)
This may help in preventing some clever hacker from attaching to the process via a debugger and capturing the program 's contents as it's being passed for the eval. |
Re^3: Blending perl and C (two approaches)
by diotalevi (Canon) on Oct 30, 2007 at 23:49 UTC
|
Perl does not have bytecode. The non-existent bytecode can't be stored and then retrieved later. If it existed, this bytecode could be deparsed back to perl code.
| [reply] |
|
|
Well, what I was referring to was the info in here. Granted, I'm a neophyte in the department of perl internals, but I've head of the -B option being used for that sort of purpose.
| [reply] |
|
|
| [reply] |
|
