Re: New syntax feedback for 4.0

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 29475
interpreted = N
texte = >> >> >> >> >> This works well for most contexts, but there are a few exceptions >> that can confuse most parsers. Specifically, ShowIf can contain >> characters like > which look just like HTML to a parser: >> >> 3> >> ^ looks a lot like followed by a 3 > >Shouldn't the parser leave stuff between alone until >webcat has substituted HTML the parser can deal with? Yes but you're missing the point. Grant is concerned about the > character being used inside the TAG, not inside the CONTEXT. Look, this illustrates the use of > inside the tag:3> ... stuff here ... The problem here is that webcat will think that the tag is instead of 3>. So the solution is to make webcat understand that the first > character in this tag is a comparison operator and that it does NOT mark the end of the tag. And that would be a hassle to code, thus the reason for my simple solution ...Just use a different comparison operator!Obviously if webcat's language recognized some character OTHER THAN > to mean greater than, this would not even be an issue.It's a lot better to use a different character for the greater than operator than to develop a bunch of new syntax for us to have to learn, that's why I suggested using ) or } instead of > as the greater than comparison operator. Then the webdna language would understand that ) or } means greater than, and this would be a non-issue.The solution would then be to use the same syntax we have always used, with the simple substitution of ONE CHARACTER, like this: ... stuff here ... ... or like this: ... stuff here ... ================================ Kenneth Grome, WebDNA Consultant 808-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:

    
  1. Re: Re[2]: New syntax feedback for 4.0 (Rob Marquardt 2000)
  2. Re: Re[2]: New syntax feedback for 4.0 (Will Starck 2000)
  3. Re: Re[2]: New syntax feedback for 4.0 (Grant Hulbert 2000)
  4. Re: Re[2]: New syntax feedback for 4.0 (Kenneth Grome 2000)
  5. Re[2]: New syntax feedback for 4.0 (Charles Kline 2000)
  6. Re[2]: Re[2]: New syntax feedback for 4.0 (jpeacock@univpress.com 2000)
  7. Re: Re[2]: New syntax feedback for 4.0 (Pat McCormick 2000)
  8. Re: Re[2]: New syntax feedback for 4.0 (Pat McCormick 2000)
  9. Re[2]: New syntax feedback for 4.0 (jpeacock@univpress.com 2000)
  10. Re: New syntax feedback for 4.0 (Kenneth Grome 2000)
  11. Re: New syntax feedback for 4.0 (Matt Helbing 2000)
  12. Re: New syntax feedback for 4.0 (Pat McCormick 2000)
  13. Re: New syntax feedback for 4.0 (Rob Marquardt 2000)
  14. Re: New syntax feedback for 4.0 (Thomas Wedderburn-Bisshop 2000)
  15. Re: New syntax feedback for 4.0 (Jesse Proudman 2000)
  16. Re: New syntax feedback for 4.0 (Brice Le Blevennec 2000)
  17. Re: New syntax feedback for 4.0 (Brice Le Blevennec 2000)
  18. Re[2]: New syntax feedback for 4.0 (jpeacock@univpress.com 2000)
  19. Re: New syntax feedback for 4.0 (Bob Minor 2000)
  20. Re: New syntax feedback for 4.0 (Grant Hulbert 2000)
  21. Re: New syntax feedback for 4.0 (Jesse Proudman 2000)
  22. Re[2]: New syntax feedback for 4.0 (jpeacock@univpress.com 2000)
  23. Re: New syntax feedback for 4.0 (jpeacock@univpress.com 2000)
  24. Re: New syntax feedback for 4.0 (Charles Kline 2000)
  25. Re: New syntax feedback for 4.0 (Peter Ostry 2000)
  26. Re: New syntax feedback for 4.0 (Thomas Wedderburn-Bisshop 2000)
  27. Re: New syntax feedback for 4.0 (Brian Wallace 2000)
  28. Re: New syntax feedback for 4.0 (Kenneth Grome 2000)
  29. Re: New syntax feedback for 4.0 (Peter Ostry 2000)
  30. Re: New syntax feedback for 4.0 (Mike Davis 2000)
  31. Re: New syntax feedback for 4.0 (Jym Duane 2000)
  32. Re: New syntax feedback for 4.0 (Grant Hulbert 2000)
  33. Re: New syntax feedback for 4.0 (Grant Hulbert 2000)
  34. Re: New syntax feedback for 4.0 (Jym Duane 2000)
  35. Re: New syntax feedback for 4.0 (Clement Ross 2000)
  36. Re: New syntax feedback for 4.0 (Chuck Rice 2000)
  37. Re: New syntax feedback for 4.0 (Nitai 2000)
  38. Re: New syntax feedback for 4.0 (Joseph D'Andrea 2000)
  39. New syntax feedback for 4.0 (Grant Hulbert 2000)
>> >> >> >> >> This works well for most contexts, but there are a few exceptions >> that can confuse most parsers. Specifically, ShowIf can contain >> characters like > which look just like HTML to a parser: >> >> 3> >> ^ looks a lot like followed by a 3 > >Shouldn't the parser leave stuff between alone until >webcat has substituted HTML the parser can deal with? Yes but you're missing the point. Grant is concerned about the > character being used inside the TAG, not inside the CONTEXT. Look, this illustrates the use of > inside the tag:3> ... stuff here ... The problem here is that webcat will think that the tag is instead of 3>. So the solution is to make webcat understand that the first > character in this tag is a comparison operator and that it does NOT mark the end of the tag. And that would be a hassle to code, thus the reason for my simple solution ...Just use a different comparison operator!Obviously if webcat's language recognized some character OTHER THAN > to mean greater than, this would not even be an issue.It's a lot better to use a different character for the greater than operator than to develop a bunch of new syntax for us to have to learn, that's why I suggested using ) or } instead of > as the greater than comparison operator. Then the webdna language would understand that ) or } means greater than, and this would be a non-issue.The solution would then be to use the same syntax we have always used, with the simple substitution of ONE CHARACTER, like this: ... stuff here ... ... or like this: ... stuff here ... ================================ Kenneth Grome, WebDNA Consultant 808-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 Kenneth Grome

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] WebDNA Sciprt for Zipping files? (2012) read and write you own cookies with webcat (1997) extending webcatalog (1997) dont want to use credit card authorisation yet (2000) Mozilla/4. and Browser Info.txt (1997) Passwords, Subscription, DBs, oh my! (2000) WebCat 3.0.7 Mac CGI & encryption (2001) WebDNA maxing out processor (2008) WebCat2: Items xx to xx shown, etc. (1997) RE: webcat license???? (1997) serial number generation (1997) post (1997) Performance Issue (2000) [shownext] link disappears after first use. Why? - because w/out the formvar, max reset to def (2000) DON'T UPGRADE, was 4.0.x find (2000) Calendar using WebCatalog? (1997) Fed Ex Rate Charts (2003) Runnaway Trigger (2007) Summing fields (1997) Webcat 4.5.1 equivalent of autonumber (2003)