Re: Parsing overhead for commenting out line endings
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 49198
interpreted = N
texte = Also, see the new Trim parameter for [getchars]... I haven't played with it yet, but it should allow you to strip returns, tabs and spaces at the beginning and end of the enclosed lines of code, something like this:[replace ...][getchars start=1&end=9999&trim=both] field1=bob &field2=mike &field3=tanya [/getchars][/replace]For pre-v5 systems, I've been using [grep] or [convertchars] with a db that strips returns and tabs to serve the same purpose. I used to use the comment method, but it makes the code hard to read and on complex pages it definitely had a noticeable performance impact. the [grep] and [convertchars] methods are much faster, and hopefully the [getchars trim=...] will be even better.- brianOn Friday, April 4, 2003, at 03:49 PM, Scott Anderson wrote:> The engine creates a new instance of the comment context for every [!] > token > it encounters. So, in the example below, the engine creates 11 context > instances (for just one iteration of the loop). Without the extra > comments, > the engine would only create 5 context instances. However, the comment > context code is fast and small, so the performance hit is not very > significant. The new [return] context was created to eliminate the > need to > use those extra comment blocks when writing a function definition, as a > convenience to the programmer. And the code will run a bit faster. > > > >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of >> Rob Marquardt >> Sent: Friday, April 04, 2003 3:08 PM >> To: WebDNA Talk >> Subject: Parsing overhead for commenting out line endings >> >> >> I was looking through the 5.0 docs when I found this under >> the [return] >> context: >> >>> [function name=add_em_up][!] >>> [/!][text]result=0[/text][!] >>> [/!][loop start=1&end=10][!] >>> [/!][text]result=[math][result]+[index][/math][/text][!] >>> [/!][/loop][!] >>> [/!][result][!] >>> [/!][/function] >>> >>> >>> Executing the above function, and wrapping the result with >> URL tags, we get: >>> 55 >>> >>> The extra 'garbage' is gone, but using all those [!][/!] >> pairs is cumbersome, >>> and does add some extra parsing overhead. >> >> Just how *much* parsing overhead? An appreciable amount? I've >> been doing >> this damn near everywhere as a matter of course for years now. >> >> [suppressReturns] didn't make it into 5.0? ; ) >> >> >> Rob Marquardt >> Designer/Resident Wirehead >> Toast Design > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Also, see the new Trim parameter for [getchars]... I haven't played with it yet, but it should allow you to strip returns, tabs and spaces at the beginning and end of the enclosed lines of code, something like this:[replace ...][getchars start=1&end=9999&trim=both] field1=bob &field2=mike &field3=tanya [/getchars][/replace]For pre-v5 systems, I've been using [grep] or [convertchars] with a db that strips returns and tabs to serve the same purpose. I used to use the comment method, but it makes the code hard to read and on complex pages it definitely had a noticeable performance impact. the [grep] and [convertchars] methods are much faster, and hopefully the [getchars trim=...] will be even better.- brianOn Friday, April 4, 2003, at 03:49 PM, Scott Anderson wrote:> The engine creates a new instance of the comment context for every [!] > token > it encounters. So, in the example below, the engine creates 11 context > instances (for just one iteration of the loop). Without the extra > comments, > the engine would only create 5 context instances. However, the comment > context code is fast and small, so the performance hit is not very > significant. The new [return] context was created to eliminate the > need to > use those extra comment blocks when writing a function definition, as a > convenience to the programmer. And the code will run a bit faster. > > > >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of >> Rob Marquardt >> Sent: Friday, April 04, 2003 3:08 PM >> To: WebDNA Talk >> Subject: Parsing overhead for commenting out line endings >> >> >> I was looking through the 5.0 docs when I found this under >> the [return] >> context: >> >>> [function name=add_em_up][!] >>> [/!][text]result=0[/text][!] >>> [/!][loop start=1&end=10][!] >>> [/!][text]result=[math][result]+[index][/math][/text][!] >>> [/!][/loop][!] >>> [/!][result][!] >>> [/!][/function] >>> >>> >>> Executing the above function, and wrapping the result with >> URL tags, we get: >>> 55 >>> >>> The extra 'garbage' is gone, but using all those [!][/!] >> pairs is cumbersome, >>> and does add some extra parsing overhead. >> >> Just how *much* parsing overhead? An appreciable amount? I've >> been doing >> this damn near everywhere as a matter of course for years now. >> >> [suppressReturns] didn't make it into 5.0? ; ) >> >> >> Rob Marquardt >> Designer/Resident Wirehead >> Toast Design > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Brian Fries
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
RE: protect tag on NT (1997)
Great product and great job ! (1997)
RE: ANother SHOWIF problem (1997)
[searchString] (1997)
ListVariables Problem (2003)
[WebDNA] WebDNA 7 multiple fcgid processes (2012)
How many lookups does it take ... (2003)
Getting Total Quantity (1997)
(1997)
Unable to view next 101-200 (1997)
too many nested tags ... (1997)
Protect and Serve (1999)
Math Problem - Format? (1997)
[shell] (2002)
How do I write this search? (2006)
Last Day of the Month (2005)
Kaaaaahhhhhhhnnnnnnn! (1997)
Extended [ConvertChars] (1997)
ISAPI WC6a and Windows 2003 Web Edition (2006)
Sample Tearoom Search Error (1997)