>>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.
yeah, ok. I _meant_ create your own <Foo> container, which I guess is the typical (though certainly not only) use for RAW_ARGS :) > > 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. right, that's the issue. but what's the alternative to reading directly from the file under the current, file-based design? or are you suggesting that nobody but core should be allowed to create <Foo> blocks? surely mod_perl's <Perl> containers can't be the only one out there in the wild? --Geoff
