Re[2]: New syntax feedback for 4.0
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 29476
interpreted = N
texte = No, no, NO, NO NOOOOOOOO!!!!There is no reason to change the obvious > to .gt. or even ). Follow the HTML standards:
3>The addition of the quotes allows any parser to distinguish between greater than and the closing >. This not something new to learn; you don't like it, stick with [showif]. This enhancement is intended to make it easier for visual HTML editors to manage with WebDNA.John Peacock ____________________Reply Separator____________________ Subject: Re: New syntax feedback for 4.0 Author: Date: 3/22/00 10:05 AM>> >> >> >> >> 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:
No, no, NO, NO NOOOOOOOO!!!!There is no reason to change the obvious > to .gt. or even ). Follow the HTML standards: 3>The addition of the quotes allows any parser to distinguish between greater than and the closing >. This not something new to learn; you don't like it, stick with [showif]. This enhancement is intended to make it easier for visual HTML editors to manage with WebDNA.John Peacock ____________________Reply Separator____________________ Subject: Re: New syntax feedback for 4.0 Author: Date: 3/22/00 10:05 AM>> >> >> >> >> 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
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:
WebCat2b15MacPlugin - showing [math] (1997)
generator prob (2001)
Parameter vs. Operator (1998)
Date problems (1997)
WebCatalog for guestbook ? (1997)
Multiple Pulldowns (1997)
[WebDNA] Downloadable docs (2011)
Separate SSL Server (1997)
Resume Catalog ? (1997)
WC2.0 Memory Requirements (1997)
Searching multiple Databases (1997)
Associative lookup style? + bit more (1997)
2.0Beta Command Ref (can't find this instruction) (1997)
Multiple security dbs (1997)
autocommit problem (1998)
Scientific notation to number, a solution? (2001)
RSS Feeds; basic info (2005)
all records returned. (1997)
[TaxableTotal] - not working with AOL and IE (1997)
Running _every_ page through WebCat ? (1997)