Bullshit. Its a text document that is parsed by a preprocessor, the
preprocessor can take arguments. This whole argument is getting rather silly,
Im amazed at the massive pushback at adding something that wont break anything,
even when CGI is still in its infancy. What happens in a year when folks want
to add something and CGI is well entrenched?
> It's worth noting that the use of that language has a certain cost. The
> simplest use of server includes --- say, something like <inc srv "|date">
> --- spawns off a Bourne shell, which does at least a couple of file system
> operations before spawning off yet another process which finally prints the
> date. A document with several includes incurs this overhead several times
> over. And, at least for those of us who have been spared AFS, spawning a
> process costs rather more than a couple of stats.
Of course, if your running on a RS/6000 with lots of memory (as I am) spawning
and executing are virtually instantaneous as its all out of ram, and nothing
ever hits the disk or network.
> In short, I don't see that the semicolon syntax is actually necessary for
> what you want to accomplish. Plausible alternatives are at least as
> convenient, and so far as I can tell (when the whole cost of running the
> retrieval is factored in) only marginally more expensive.
It is rediculus that to serve up documents I must spawn a huge scripting
language to emulate a server (which I already have running!).
This morning I absolutely needed the semicolon syntax to accomplish what I want
in any clean manner. It took exactly 2 additional lines of code to the server.
Im still amazed at the inflexibilty you folks are imposing on something so new,
that hasnt even begun to be used in all possible situations it has been
designed for. Its okay, I dont mind adding 2 lines of code to every new
release, its too bad that everyone who finds themselves in my position will
also need to do so.
-Crh
Charles Henrich Michigan State University henrich@crh.cl.msu.edu
http://rs560.msu.edu/~henrich/