Two things.
1. I was thinking of optimize in the BBEdit sense -- compacting the
results to remove non-semantic content (aka noise or entropy).
Unfortunately sometimes the unwanted white space has meaning (for
example contructing a post) and I must sacrifice readability for
function. I would use <@optimize> primarily for this purpose.
2. I wasn't thinking of performance optimization, but now that you
mention it, if the server is given a "compiler directive" the
resulting code is more compact, thereby saving memory and time on
subsequent requests.
Bill
William M. Conlon, P.E., Ph.D.
To the Point
2330 Bryant Street
Palo Alto, CA 94301
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
On Jan 25, 2007, at 10:02 AM, Ben Johansen wrote:
But, isn't the time to run this tag directly proportional to the
extra time the non optimize code takes, yielding the same time to
process the code an maybe more time due to optimize overhead
Ben
On Jan 25, 2007, at 9:18 AM, William M Conlon wrote:
<@optimize [string]></@optimize>
default string is tab, space, linefeed, carriage return
<@optimize> tells the server to compact the witango code to remove
the [default|specified] characters. This indicates that the
specified characters are included only for readability, and do not
need to be included in the ResultsHTML.
This tag has no effect on the Results of metags, as it is applied
before the code is executed.
Bill
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
