Re[4]: Problem with new formvariables
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 31226
interpreted = N
texte = Grant - That is exactly why the is a better idea; you just need a single branch at the top of the parser (old vs new). If you allow any number of variable to be insecure, you will need to have a much more complicated parser. By going all or nothing with the above tag, you can simply keep the old parse code in parallel with the new with a single branch.I urge you to not wither under the complaints of people who need to make thousands of changes. I suspect many if not most people who are complaining about these changes have not thoroughly tested their existing sites to see where things break and why (with the possible exception of Ken). I am going to finally get the new version installed on Linux and copy my sites over and see what works. I suspect that everything will; I have never used that style of coding.John Peacock ____________________Reply Separator____________________ Subject: Re[3]: Problem with new formvariables Author:
Date: 5/2/2000 10:38 AM>I'm mostly curious how Grant feels about the compromise ideas like >[TEXT SECURE=F]If it's possible to do, this is the most likely candidate. Technically there has only been one working day (Monday) since the release of the beta, so excuse us if we don't have all the answers just yet. Having two [text] variable namespaces (one before, and one after the hierarchy in question), has unknown consequences to the parser.Grant Hulbert, Director of Engineering ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive, #380 | ------------------------- San Diego, CA 92127 | Software & Site Development Main Line: (858) 675-1106 | http://www.smithmicro.com Fax: (858) 675-0372 ********************************** ############################################################# 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:
Grant - That is exactly why the is a better idea; you just need a single branch at the top of the parser (old vs new). If you allow any number of variable to be insecure, you will need to have a much more complicated parser. By going all or nothing with the above tag, you can simply keep the old parse code in parallel with the new with a single branch.I urge you to not wither under the complaints of people who need to make thousands of changes. I suspect many if not most people who are complaining about these changes have not thoroughly tested their existing sites to see where things break and why (with the possible exception of Ken). I am going to finally get the new version installed on Linux and copy my sites over and see what works. I suspect that everything will; I have never used that style of coding.John Peacock ____________________Reply Separator____________________ Subject: Re[3]: Problem with new formvariables Author: Date: 5/2/2000 10:38 AM>I'm mostly curious how Grant feels about the compromise ideas like >[TEXT SECURE=F]If it's possible to do, this is the most likely candidate. Technically there has only been one working day (Monday) since the release of the beta, so excuse us if we don't have all the answers just yet. Having two [text] variable namespaces (one before, and one after the hierarchy in question), has unknown consequences to the parser.Grant Hulbert, Director of Engineering ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive, #380 | ------------------------- San Diego, CA 92127 | Software & Site Development Main Line: (858) 675-1106 | http://www.smithmicro.com Fax: (858) 675-0372 ********************************** ############################################################# 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:
[WebDNA] get vs post problems (2011)
Latin Characters (1998)
rotating thumbnails (1997)
Extended [ConvertChars] (1997)
[WebDNA] generic Ajax question: storing a variable site-wide (2009)
Database Helper Update (1998)
Multiple Search Fields (1998)
What file? (1997)
more ! testing (1997)
writing db to disk (1997)
Type 11 errors setting up WebCAt 2 (1997)
totals (1997)
strange [date] behavior (2001)
OR-searching (2000)
REPOST: How do _you_ back up your db? (2000)
[OT] What log analyzer do you use? (2000)
MS Commerce Comparison (long) (1998)
[WebDNA] plupload ? (2012)
Too Much Rootbeer Free Offer (1997)
Carriage returns in [text] variables (1999)