Yes, that makes sense. Perhaps an optional argument for Execute that lists
the variables to export?
yes, that's what I want to do
Actually, there has to be a way to get variables
in both directions. Perhaps an export list and an import list in the
params to Execute?
one list should be
Hi Steve,
From Steve Willer:
This looks pretty neat. I don't think I told you, but I started at a new
job last October, and immediately spearheaded an effort to replace their
internal template system with an Embperl-based system. Well, I won. :-)
:-)
However, the template language itself
On Mon, 14 Feb 2000, Gerald Richter wrote:
If you really like to do so, we have to compile the perl (of every object)
for every namepsace it will run into. Currently I think more of a feature
like exporting variables (like Perl modules can do), so that they are
visible in all object during
