Re: [WebDNA] SWITCH/CASE or SHOWIF
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 101491
interpreted = N
texte = On 20 Nov 2008, at 20:24, Govinda wrote: >> 1. To go through 100 different choices, is a switch/case more >> efficient or 100 showif statements more efficient? > I dunno, I would guess that one switch case is faster; at least in > other languages, when you evaluate once instead of many times, it's > faster. >> >> >> 2. In the final generated HTML code, when 100 SHOWIF statements are >> processed, but only 1 is actually shown, the other 99 SHOWIF >> statements create line breaks. Is there a way to prevent the line >> breaks from showing up if a showif does not evaluate to true? > anywhere you don't want the line break to appear when webdna spite > out the html then just wrap it with the webdna comment tag, like > this one [!] > [/!] I find coding like this a bit annoying I prefer the newer [function name=myfunction] put stuff in here and it won't show... [text scope=golbal]var1=foo[/text] [text]var2=bar[/text] [return]anything you want displayed[/return] [/function] [myfunction] This example would return "\r \ranything you want displayed" The two carriage returns are the space in between the end of /function and the bit where it was called Worth noting that if you then called the following: var1=[var1] and var2=[var2] this would return var1=foo and var2=[var2] as to reference a variable outside a function, you need to specify [text scope=global] > >> >> >> 3. Does a SWITCH/CASE statement create line breaks for all the >> cases that evaluate to false? > if it does , then try the trick I just mentioned. >> > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/
Associated Messages, from the most recent to the oldest:
On 20 Nov 2008, at 20:24, Govinda wrote: >> 1. To go through 100 different choices, is a switch/case more >> efficient or 100 showif statements more efficient? > I dunno, I would guess that one switch case is faster; at least in > other languages, when you evaluate once instead of many times, it's > faster. >> >> >> 2. In the final generated HTML code, when 100 SHOWIF statements are >> processed, but only 1 is actually shown, the other 99 SHOWIF >> statements create line breaks. Is there a way to prevent the line >> breaks from showing up if a showif does not evaluate to true? > anywhere you don't want the line break to appear when webdna spite > out the html then just wrap it with the webdna comment tag, like > this one [!] > [/!] I find coding like this a bit annoying I prefer the newer [function name=myfunction] put stuff in here and it won't show... [text scope=golbal]var1=foo[/text] [text]var2=bar[/text] [return]anything you want displayed[/return] [/function] [myfunction] This example would return "\r \ranything you want displayed" The two carriage returns are the space in between the end of /function and the bit where it was called Worth noting that if you then called the following: var1=[var1] and var2=[var2] this would return var1=foo and var2=[var2] as to reference a variable outside a function, you need to specify [text scope=global] > >> >> >> 3. Does a SWITCH/CASE statement create line breaks for all the >> cases that evaluate to false? > if it does , then try the trick I just mentioned. >> > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/
Toby Cox
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:
Authorize net woes (2003)
autosensing lanague selection (1997)
any limitations on # of users.db entries (1999)
Accessing Storebuilder (2000)
Webstar 1.3.1 PPC (1997)
Does not begin with.... (2003)
Context and commands (1998)
Pithy questions on webcommerce & siteedit (1997)
[format xs] freeze (1997)
[writefile] (1997)
WC2f3 (1997)
PCS Frames (1997)
UnitShipCost Slight Return (2003)
WebCat2b15MacPlugin - [protect] (1997)
Adding insurance to an order, round 2 (2003)
Fun with dates (1997)
protect tag on NT (1997)
Images (2000)
POST Datamissing? (1998)
WC2b15 File Corruption (1997)