Re: Naming a module that injects new code into a file's source at compile time

2011-11-02 Thread John M. Gamble
On 11/1/2011 11:03 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

Re: Naming a module that injects new code into a file's source at compile time

2011-11-01 Thread Eric Strom
On Nov 1, 9:02 pm, dpchr...@holgerdanske.com (David Christensen) wrote: > How about "Macro"?  Oh, that name is already taken (both capitalized and > lowercase): > >      http://search.cpan.org/~segv/Macro-0.2/Macro.pod > >      http://search.cpan.org/~gfuji/macro-0.06/lib/macro.pm > > Are there mor

Re: Naming a module that injects new code into a file's source at compile time

2011-11-01 Thread David Christensen
On 11/01/2011 09:03 AM, Eric Strom wrote: > I am working on a module and set of tools for injecting source into > another file at compile time. ... > The overall goal of the module is to allow people to write a macro > function: > sub my_0 {map "my \$$_ = 0", @_} > And then be able to write:

Naming a module that injects new code into a file's source at compile time

2011-11-01 Thread Eric Strom
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