Re: Preventing code execution

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 48546
interpreted = N
texte = Hi Donovan,I would assume it is because the first [raw] actually stops the parsing of the material inside the context. Therefore it doesn't really see the next [raw] tag. That is probably because the finite state machine that parses out the webdna code only allows one state to execute after the initial [raw] context, and that would be a [/raw]. I haven't seen the code for this but that is how I would program the parser if I were doing it anyway. hth,Larry Goodhew > > John Hill wrote: > > >There's a good reason for this - if [raw] doesn't parse, then coming across a > >[raw] tag inside a [raw] tag should do nothing. Of course, the only tag it does > >parse is [/raw]. Thus nested [raw] means the outer most [raw] starts the > >parsing the and inner most [/raw] stops it which will cause all sorts of odd > >behavior - this is not a bug though. > > > It may have been meant to work this way but I guess I don't see the point. > > It just makes it difficult to display *all* [...]. Do you know why it was > created this way? > > Donovan > > > > > > -- > -Donovan Brooke > -Administrator of IT / > -Assc. Art Director > -Creative Services > -Epsen Hillmer Graphics > > -402.342.1169 X297 > > > > > ------------------------------------------------------------- > 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 > Web Archive of this list is at: http://webdna.smithmicro.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 Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Preventing code execution (Larry Goodhew 2003)
  2. Re: Preventing code execution (Donovan 2003)
  3. Re: Preventing code execution (John Hill 2003)
  4. Re: Preventing code execution (Gary Krockover 2003)
  5. Re: Preventing code execution (Donovan 2003)
  6. Re: Preventing code execution (Rob 2003)
  7. Re: Preventing code execution (Donovan home EHG 2003)
  8. Re: Preventing code execution (Rob 2003)
  9. Re: Preventing code execution (Joe D'Andrea 2003)
  10. Re: Preventing code execution (Kenneth Grome 2003)
  11. Re: Preventing code execution (Gary Krockover 2003)
  12. Re: Preventing code execution (Rob 2003)
  13. Re: Preventing code execution (Kenneth Grome 2003)
  14. Re: Preventing code execution (Rob 2003)
  15. Re: Preventing code execution (Stuart Tremain 2003)
  16. Re: Preventing code execution (Joe D'Andrea 2003)
  17. Re: Preventing code execution (John Hill 2003)
  18. Re: Preventing code execution (Alain Russell 2003)
  19. Re: Preventing code execution (Jay Van Vark 2003)
  20. Re: Preventing code execution (Craig Forest 2003)
  21. Re: Preventing code execution (Jay Van Vark 2003)
  22. Preventing code execution (Craig Forest 2003)
Hi Donovan,I would assume it is because the first [raw] actually stops the parsing of the material inside the context. Therefore it doesn't really see the next [raw] tag. That is probably because the finite state machine that parses out the webdna code only allows one state to execute after the initial [raw] context, and that would be a [/raw]. I haven't seen the code for this but that is how I would program the parser if I were doing it anyway. hth,Larry Goodhew > > John Hill wrote: > > >There's a good reason for this - if [raw] doesn't parse, then coming across a > >[raw] tag inside a [raw] tag should do nothing. Of course, the only tag it does > >parse is [/raw]. Thus nested [raw] means the outer most [raw] starts the > >parsing the and inner most [/raw] stops it which will cause all sorts of odd > >behavior - this is not a bug though. > > > It may have been meant to work this way but I guess I don't see the point. > > It just makes it difficult to display *all* [...]. Do you know why it was > created this way? > > Donovan > > > > > > -- > -Donovan Brooke > -Administrator of IT / > -Assc. Art Director > -Creative Services > -Epsen Hillmer Graphics > > -402.342.1169 X297 > > > > > ------------------------------------------------------------- > 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 > Web Archive of this list is at: http://webdna.smithmicro.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 Web Archive of this list is at: http://webdna.smithmicro.com/ Larry Goodhew

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:

multiple db's (2003) Re1000001: Setting up shop (1997) Our Webcat site launched (1997) 2.0 Info (1997) RE: Web*SSL and WebCatalog (1997) Shared Webstar Directory (1998) Upload and WebCat (1998) WebCat2 - [format thousands] (1997) Separate SSL Server (1997) Thanks Grant (1997) Running _every_ page through WebCat ? (1997) autosensing lanague selection (1997) WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997) [search] & [encrypt]/[decrypt] (2001) OT : Java problems (2002) Text data with spaces in them... (1997) [OT] Live Chat with Video capability (2008) webcat nt (1997) UPDATE PROBLEM (1997) how do you and/or in a search? (1997)