Re: Scoping rules in WebDNA 4.0
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 29425
interpreted = N
texte = > Lazy scoping is fine, as long as the rules are stated explicitly, so we can > determine the precedence. I have no problem with the thought that the same > variable name can have different meanings depending on the context that > contains it, but then I am a Perl Hacker in real life ;~0 > > [dbname.date] vs [cart.date] vs [sys.date] > > John PeacockThis one. Right Here. it's simple, clean, perfect. if you are in two nested searches in two databases, with the same field names... you will simply specify which database in the variable name!Beginners will understand it, because it makes sense.Hey, while we are at it, how about having WebCatalog understand that data inside a variable name is just that (data) and it should ignore any operations it sees... think of it as Pre[url]ing the data on both sides of a showif or a hideif.Thanks for allowing the input! Brian B. Burton BOFH - Department of Redundancy Department --------------------------------------------------------------- MMT Solutions - Specializing in Online Shopping Solutions 973-808-8644 http://www.safecommerce.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 To switch to the INDEX mode, E-mail to Send administrative queries to
Associated Messages, from the most recent to the oldest:
> Lazy scoping is fine, as long as the rules are stated explicitly, so we can > determine the precedence. I have no problem with the thought that the same > variable name can have different meanings depending on the context that > contains it, but then I am a Perl Hacker in real life ;~0 > > [dbname.date] vs [cart.date] vs [sys.date] > > John PeacockThis one. Right Here. it's simple, clean, perfect. if you are in two nested searches in two databases, with the same field names... you will simply specify which database in the variable name!Beginners will understand it, because it makes sense.Hey, while we are at it, how about having WebCatalog understand that data inside a variable name is just that (data) and it should ignore any operations it sees... think of it as Pre[url]ing the data on both sides of a showif or a hideif.Thanks for allowing the input! Brian B. Burton BOFH - Department of Redundancy Department --------------------------------------------------------------- MMT Solutions - Specializing in Online Shopping Solutions 973-808-8644 http://www.safecommerce.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 To switch to the INDEX mode, E-mail to Send administrative queries to
Brian B. Burton
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:
Formulas.db + Users.db (1997)
php vs WebCatalog (2000)
WebCatalog/Mac 2.1b2 - PIXO (1997)
PCS Emailer's role ? (1997)
[append] problems (2003)
Separate SSL Server (1997)
[REFERRER] works with form posts (2003)
[Sum] function? (1997)
Middle Context (2002)
Re:no [search] with NT (1997)
Multiple Pulldowns (1997)
Re:E-Mailer (WebCatb15acgiMac) (1997)
upload pictures any solution (1999)
shipping costs (1997)
Database causes out of memory error (2000)
Email Problem (1997)
Follow-Up to: Removing [showif] makes a big difference in speed (1997)
Variable security (2000)
Last Record not recognized? (1999)
Webcat 2.0.1b1 bug with IE 3.01/4.0p1 (1997)