Hi Stas - > As a followup to the discussed issue, we need to redefine the concept of: > > "put those things in startup.pl" > > we now need to say: > > "put those things in post_config phase handler" [...] > So there is a possibility to introduce a new directive: PerlStartupFile > (feel free to suggest a better name) which will be: > > PerlStartupFile "somefile.pl" [...] > after discussing this with gozer on irc we aren't sure this is a good > idea, as for most people using the old startup.pl concept will still work.
Leaving things as-is sounds like it might be asking for trouble, e.g. people not aware of the implications between config and post-config, or people still using "PerlRequire startup.pl" from their mp1 setup and it works ok by coincidence, and suddenly stops working (or fails in mysterious ways) when they add something that unknowingly breaks the rules about config vs. post-config phases. Maybe it would also help to introduce an alias for PerlRequire called something like PerlConfigFile, to make it more obvious it should only be used to modify config, and recommend that instead of using "PerlRequire startup.pl" people should do: PerlConfigFile "some-file.pl" PerlStartupFile "some-other-file.pl" Or maybe since there is already PerlPostConfigHandler, parallel that and use the name PerlPostConfigFile instead of PerlStartupFile?: PerlConfigFile "some-file.pl" PerlPostConfigFile "some-other-file.pl" (Don't know about that, maybe PerlStartupFile seems more intuitive about what you'd use it for...) Larry Leszczynski --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
