Re: Unexpected comparison behavior change in 4.5.1

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 48758
interpreted = N
texte = On Monday, March 17, 2003, at 10:38 PM, Charles Kline wrote:> > On Tuesday, March 18, 2003, at 01:32 AM, Brian Fries wrote: > >> [showif bob^] >> >> or >> >> [if bob^] >> >> >> In my tests, these evaluate to true under 4.5.0 and earlier, and to >> false under 4.5.1. Clearly URL is not the issue here. >> > [showif bob^] should evaluate to 'false' so it seems the bug was in > 4.5.0And WHY should [showif bob^] evaluate false? I don't see anything in the empty string that isn't also in bob, therefore I - and every version of WebDNA prior to 4.5.1 - would expect it to evaluate to true.> > [if bob^] should evaluate to 'false' as well. >Again, why is false any better than true for this? If WebDNA were being written from scratch, then it would be the right time to make a choice on this. But, since it's worked the same way since I began using the product in 1997, I think its a little late to make this change.I'm not really here to debate which way it SHOULD resolve the comparison, I'm only here to point out that it broke my code - which was fully tested and had been working fine for years.> It was always my understanding that when using [if] to compare > strings, they needed to be in quotes. Was in the docs. as that from > the beginning. >Relevance? What quotes do you see missing from my example?- brian ------------------------------------------------------------- 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: Unexpected comparison behavior change in 4.5.1 (John Peacock 2003)
  2. Re: Unexpected comparison behavior change in 4.5.1 (Charles Kline 2003)
  3. Re: Unexpected comparison behavior change in 4.5.1 (Brian Fries 2003)
  4. Re: Unexpected comparison behavior change in 4.5.1 (Velma Kahn 2003)
  5. Re: Unexpected comparison behavior change in 4.5.1 (Clint Davis 2003)
  6. Re: Unexpected comparison behavior change in 4.5.1 (Clint Davis 2003)
  7. Re: Unexpected comparison behavior change in 4.5.1 (Charles Kline 2003)
  8. Re: Unexpected comparison behavior change in 4.5.1 (Velma Kahn 2003)
  9. Re: Unexpected comparison behavior change in 4.5.1 (Charles Kline 2003)
  10. Re: Unexpected comparison behavior change in 4.5.1 (Brian Fries 2003)
  11. Re: Unexpected comparison behavior change in 4.5.1 (Charles Kline 2003)
  12. Re: Unexpected comparison behavior change in 4.5.1 (Kenneth Grome 2003)
  13. Re: Unexpected comparison behavior change in 4.5.1 (Brian Fries 2003)
  14. Re: Unexpected comparison behavior change in 4.5.1 (Charles Kline 2003)
  15. Re: Unexpected comparison behavior change in 4.5.1 (Brian Fries 2003)
  16. Re: Unexpected comparison behavior change in 4.5.1 (Alain Russell 2003)
  17. Re: Unexpected comparison behavior change in 4.5.1 (Stuart Tremain 2003)
  18. Re: Unexpected comparison behavior change in 4.5.1 (Rob Marquardt 2003)
  19. Re: Unexpected comparison behavior change in 4.5.1 (Brian Fries 2003)
  20. Re: Unexpected comparison behavior change in 4.5.1 (Gary Krockover 2003)
  21. Re: Unexpected comparison behavior change in 4.5.1 (Alain Russell 2003)
  22. Re: Unexpected comparison behavior change in 4.5.1 (Tim Robinson 2003)
  23. Unexpected comparison behavior change in 4.5.1 (Brian Fries 2003)
On Monday, March 17, 2003, at 10:38 PM, Charles Kline wrote:> > On Tuesday, March 18, 2003, at 01:32 AM, Brian Fries wrote: > >> [showif bob^] >> >> or >> >> [if bob^] >> >> >> In my tests, these evaluate to true under 4.5.0 and earlier, and to >> false under 4.5.1. Clearly URL is not the issue here. >> > [showif bob^] should evaluate to 'false' so it seems the bug was in > 4.5.0And WHY should [showif bob^] evaluate false? I don't see anything in the empty string that isn't also in bob, therefore I - and every version of WebDNA prior to 4.5.1 - would expect it to evaluate to true.> > [if bob^] should evaluate to 'false' as well. >Again, why is false any better than true for this? If WebDNA were being written from scratch, then it would be the right time to make a choice on this. But, since it's worked the same way since I began using the product in 1997, I think its a little late to make this change.I'm not really here to debate which way it SHOULD resolve the comparison, I'm only here to point out that it broke my code - which was fully tested and had been working fine for years.> It was always my understanding that when using [if] to compare > strings, they needed to be in quotes. Was in the docs. as that from > the beginning. >Relevance? What quotes do you see missing from my example?- brian ------------------------------------------------------------- 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/ Brian Fries

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:

PCS Customer submissions ? (1997) Late on Friday.... brain fried (2002) User Authentication (2003) Re:Off Topic: Frames Killer? (1998) Secure server question (1997) Need relative path explanation (1997) Help! WebCat2 bug (Ben's input) (1997) [OT] (waaaay OT) further off topic than before (2004) WebCatalog can't find database (1997) WC2.0 Memory Requirements (1997) taxrate (1999) selectively replacing records within a [founditems] (2000) OT New use for WebCat (1998) [format] problem (2001) Stats (2001) _ in front of field name (1998) Can I invoke an ssi plugin from within a webcat page (1997) MacOS 9 => ODBC=> Ms SQL Server 7 (2000) searchable list archive (1997) Simple way to create unique SKU (1997)