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:

[INCLUDE] Limitations (1998) RE: Languages (1997) Roundup function? (1997) PCS Customer submissions ? (1997) problems with 2 tags (1997) Configuring E-mail (1997) Images do not upload completely ... (2003) Multiple catalog databases and showcart (1997) price change help (1998) Searching multiple fields from one form field (1997) Database location (2002) Calculating multiple shipping... (1997) Am I going senile? (Price recalc based on quantity) (1997) Is [variable] a Number? (2007) Simple way to create unique SKU (1997) Using [showif] (2000) RE: Can a database get stomped by simultaneous access? (1997) Search/sort in URL Was: GuestBook example (1997) WebCat2 several catalogs? (1997) Initiating NewCart (1997)