On Sat, Aug 10, 2002 at 02:24:34PM -0400, sungo wrote: > > On Saturday, August 10, 2002, at 02:18 PM, Rocco Caputo wrote: > > >I would like to avoid preprocessing if at all possible. Even source > >filters cause problems with some people-- especially those who want to > >deploy programs using perlapp or perl2exe. I think I would start over > >if it came to that. > > in my copious free time (right...), i'm designing a Parse::RecDescent > grammar to potentially replace POE::Preprocessor. the upside? it will > allow us to precompile core POE modules for use in perlapp or perl2exe > (or rather, will allow YOU to do so :). i dont have a prototype as of > yet but i've got some ideas and sometime in the near future i'll have > something for you guys to play with.
Umm... I solved this already. POE::Preprocessor now honors the POE_PREPROC_DUMP environment variable. It should be set to the base directory where POE::Preprocessor will excrete expanded files. Subdirectories of POE_PREPROC_DUMP can be added to PERL5LIB, and then perlapp or perl2exe can generate stand-alone POE EXEs. That's still far too much work for everyday coding. -- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sf.net
