Go back to
Re: On Scripting versus Compiled solutions and read the following sentence,
...I don't think a bundlemonkey approach (binding the interpreter and the bytecode together into an executable package) will do the trick.
The approach that you suggest (including the compiler with the binary) is exactly the "bundlemonkey" approach that jonadab ruled out. And my claim is that if you rule that out, then you run into problems with eval.
Well..I'm not sure what he would think of Squeak's approach (decompile the running environment into C++ code which, when compiled again, gives you the same environment again). That isn't the usual "bundlemonkey" approach, but it isn't totally dissimilar either...