Re[3]: Re[3]: Problem with new formvariables

This WebDNA talk-list message is from

2000

It keeps the original formatting. numero = 31240
interpreted = N
texte = No, that is the truth. Your specific problem was that you assumed that sinceyour (badly named) variable [max] worked across some contexts it would workacross all. You assumed something about the context that was not true. Yourhard and fast rule about variable priorities was wrong, pure and simple, withregards to [search] and [max]. Go back to the earliest 3.x release and see ifit is still there; your paranoia is getting out of control (again).John Peacock____________________Reply Separator____________________Subject: Re[2]: Re[3]: Problem with new formvariables Author: Date: 5/2/2000 8:35 AM>For a really good example why it is not a good idea to rely on >context sensitive>variables, look up the running discussion two months ago or so with Ken>regarding a variable called [max].This is absolutely untrue. My specific problem actually stemmed from SM's experimentation with the new [max] tag in the latest 3.x release without telling anyone about it, it had nothing whatsoever to do with improper use of context-sensitive variables.================================Kenneth Grome, WebDNA Consultant808-737-6499 http://webdna.net================================#############################################################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:

Re[3]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)

No, that is the truth. Your specific problem was that you assumed that sinceyour (badly named) variable [max] worked across some contexts it would workacross all. You assumed something about the context that was not true. Yourhard and fast rule about variable priorities was wrong, pure and simple, withregards to [search] and [max]. Go back to the earliest 3.x release and see ifit is still there; your paranoia is getting out of control (again).John Peacock____________________Reply Separator____________________Subject: Re[2]: Re[3]: Problem with new formvariables Author: Date: 5/2/2000 8:35 AM>For a really good example why it is not a good idea to rely on >context sensitive>variables, look up the running discussion two months ago or so with Ken>regarding a variable called [max].This is absolutely untrue. My specific problem actually stemmed from SM's experimentation with the new [max] tag in the latest 3.x release without telling anyone about it, it had nothing whatsoever to do with improper use of context-sensitive variables.================================Kenneth Grome, WebDNA Consultant808-737-6499 http://webdna.net================================#############################################################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 jpeacock@univpress.com

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:

WebCat on Alpha? (1997) WC2.0 Memory Requirements (1997) WebMerchant still not working!! (1999) Friday brain fry (2001) [OT] Display Glitch (2004) [WebDNA] WebDNA7 and mod_fcgi (2013) [SHOWIF AND/OR] (1997) Help (1999) switching users (1998) SKU (1997) [WebDNA] CMS in WEBDNA (2009) WCS Newbie question (1997) NT considerations (1997) Quickie question on the email templates (1997) switching users (1998) Zipcodes (1998) Online Docs? (1997) New servers and new inline cache (1997) a new bug? (1999) WC Database Format (1997)