Perrin Harkins wrote:
This sounds great, but the code snippet you included makes it look like
the rand() value will have an effect on the number of bytes returned.
This is probably not a good idea, since that would allow many other
factors to affect the results. I suggest making sure that
At 03:53 PM 12/17/00 -0800, Joshua Chamas wrote:
Hey,
2+ levels of code layering
1 rand() value per request
6 for loops executed
20 additions (float integer)
10 lval assignments
200 variables inline
202+ chuncks of static html rendered
Over 2900 byte template to parse
Gunther Birznieks wrote:
And a partridge in a pear tree :) Sorry... it's just stupid xmas carols.
You've got the spirit. :)
Anyway, if you are splitting out the DB side for later then why not do the
same for language features and template features? Here they are both rolled
into one
On Mon, 18 Dec 2000, Joshua Chamas wrote:
The rand() is only in there to prevent a language compiler
from rendering the whole thing static if it were able to
guess that all of the variables would be knowable by
unwinding the for loops.
Instead of using a random number, why don't you pas
Hey,
I'd like some comments on the Hello World 2000 benchmark that
I am creating. One of the great failings of the Hello World
benchmark is that it doesn't address the runtime execution
of various web application environments.
Perl is oft stated to provide better runtime execution for web
Joshua Chamas wrote:
Hey,
I'd like some comments on the Hello World 2000 benchmark that
I am creating. One of the great failings of the Hello World
benchmark is that it doesn't address the runtime execution
of various web application environments.
It seems that the assumption of a
Joshua Chamas wrote:
The first of these runtime benchmarks is geared towards templating
or embedded environments like ASP,PHP,Embperl,JSP,Mason ... the
Hello World 2000 benchmark below has these characteristics:
2+ levels of code layering
1 rand() value per request
6 for loops
