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

Thanks for the feedback. So do you think I should simultaneously post to module-authors and p5p? Or hit module-authors first? On Mon, Oct 31, 2011 at 3:16 AM, Steffen Mueller wrote: > Generally speaking, you're much more likely to get useful feedback if you > post to the module-authors list or

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

On 10/31/2011 09:47 PM, Eric Strom wrote: Thanks for the feedback. So do you think I should simultaneously post to module-authors and p5p? Or hit module-authors first? Don't cross-post on these lists, please. Too many subscribers. :) I'd say try module-authors first. Cheers, Steffen

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

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

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

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