Posted by Steven Borrelli on 06/22/07 14:46

On Jun 21, 8:31 am, Michael Fesser <neti...@gmx.de> wrote:
> .oO(Jerry Stuckle)
>
> >Interesting, because I've seen this before, and others have commented on
> >it, also. Maybe it was a bug in an older version of PHP - it's been a
> >while ago. But I had one local cohort who was using php includes (not
> >SSI), and his files were not being parsed when they had .inc extensions.
>
> Either a bug or something heavily wrong on the server. As mentioned in
> another post -- PHP includes have _nothing_ to do with the web server,
> they are entirely handled by the interpreter. Since you explicitly write
> their name in the include statement, you can call them whatever you
> like:
>
> require_once 'foo.bar';
> require_once '42';
> require_once '.o0o.';
>
> All valid.
>
> Micha

When you say the PHP includes have nothing to do with the web server,
that is somewhat confusing.

If I have my index.php, and I have a call to a php include within
that, and also another php include within the first include, and all
the includes have the .php file extension, will everything be parsed
and appear like it's supposed to? And it won't work if the file
extension is different?

In other words, is it possible to make nesting php includes?

Steven

[Back to original message]