> > > The first is boolean - whether to look for php tags of any sort in the > file. The default needs to be to expect them, this is the backwards > compatible behavior, and I'm thinking this should be 0. 1 means "no > tags in file". This means the file to be included can be written > without any php tags at all. This might allow the parser to speed up, > but that would be a side benefice to two goals. >
I don't like this, I mean one can end up printing out his sourcecode if - those files are publically available through the document root or - if he somewhere used a wrong argument, and includes a tagless file with the (default) with-tags option. on the other hand, a html file page with php code examples (but without php tags) could be turned into executing those examples if the tagless option is used. I would support the namespace option though. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
