Parsing overhead for commenting out line endings

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 49196
interpreted = N
texte = 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 Design800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.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:

    
  1. Re: Parsing overhead for commenting out line endings (Scott Anderson 2003)
  2. Re: Parsing overhead for commenting out line endings (Brian Fries 2003)
  3. Re: Parsing overhead for commenting out line endings (Scott Anderson 2003)
  4. Parsing overhead for commenting out line endings (Rob Marquardt 2003)
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 Design800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.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/ Rob Marquardt

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:

Format Thousands Looks Busted (2000) webcat- multiple selection in input field (1997) FRAMES and CART tags problem??!? (1999) Possible Bug in 2.0b15.acgi (1997) More! on [ShowCart] and GET vs. POST (1997) Mail Server Needed. (1998) Help! WebCat2 bug (1997) [Summary] re: Emailer setup (1997) NT - Thanks and Taxes (1997) Shipping formula problem (1997) OK, here goes... (1997) [WebDNA] Error. WebDNA (version 5.1g or later) is not running. (2013) External Images (1998) RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (2020) [WebDNA] A good PDF reference for beginners (2011) hiding blank fields (2003) WC TableGrinder (1997) A multi-processor savvy WebCatalog? (1997) [convertchars] (2000) WebCatalog Mac 2.1b3 (1997)