Actually, no I wouldnt suggest using a ';' to represent executable. The
current manner to determine if a script is a script is "good enough". In fact
using the ';' to determine if a script was would disallow most of what Im
doing. I use the inlined include facility of NCSA's server extensivly. I want
the server to return
And then the document calls an inlined include which can then decipher the ';'
attributes, making all sorts of interesting things possible.
I'd like to say, this syntax could be *in addition* to the current method, it
doesnt need to replace it. Im finding a situation here where the forced
"stat'ing" of non-existant files to be distasteful, wasteful, and a very
potential problem with servers that are heavily utilized.
Charles Henrich Michigan State University email@example.com