On Mon, Nov 29, 2004 at 01:54:18PM -0500, Geoffrey Young wrote: > Justin Erenkrantz wrote: > > --On Monday, November 29, 2004 10:41 AM -0800 Greg Stein > > <[EMAIL PROTECTED]> wrote: > > > >> but we were not allowed to remove features. Removing the fp from the > >> API would have disabled this "feature" in mod_perl, among others. > > > > I can't tell you how often I've been bitten personally by mod_perl > > trying to reparse our configuration because of this 'feature.' It needs > > to go away big time. > > sorry, but I'm not following. can you guys be specific (code wise) about > what is supposed to be forbidden? my only knowledge of mod_perl using that > file pointer is when implementing <Foo> containers where we (of course) need > to know what is between the opening and closing markers.
Yup. That's the one. And to do that, you use the file pointer which gets passed out thru the API. > but in that > respect, we are no different from any other module that wants to implement a > RAW_ARGS directive... Hardly. RAW_ARGS takes a single line of text. No file pointer. That line could come from anywhere. The container stuff takes a file pointer and reads arbitrary amounts of input from the file. There is no way that the core parser can snarf up the text and pass that block to you [independent of the fp] since the syntax could be arbitrary. Cheers, -g -- Greg Stein, http://www.lyra.org/
