Generally speaking, you're much more likely to get useful feedback if
you post to the module-authors list or blog about it. modules@perl.org
is mostly an administrative list of PAUSE admins and we're spread a bit
thin.
On 10/30/2011 02:32 AM, Eric Strom wrote:
I am working on a module and set of tools for injecting source into
another file at compile time. It currently does this by using
Filter::Util::Call to hook into the compilation process, inject the
new code before the next line that perl will compile, and then remove
itself handing control back to the compiler.
How nasty...
I have tentatively named this module `eval.pm`
use eval 'my $x = 1';
use eval some_sub(...);
since `use` implies compile time and it is injecting the source into
the currently compiling `eval`.
but I am considering any of the following names:
Technically, any lower-case name needs approval from perl5-porters since
they're reserved for use by the core. Ignoring this issue (you could
always ucfirst):
eval
Makes some sense, but I'd say it's not specific enough.
insert
Way too overloaded.
inject
inline
I'd say both of these make a sense.
compile
Hmm, you're not really compiling as such, so...
here
I think that's bound to confuse people greatly.
Best regards,
Steffen
