Re: Another new bug found ...

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 34028
interpreted = N
texte = >agreed that an advance warning would have been nice in this case of >no spaces in >fieldnames (one perhaps small change on the side of the parser's >behaviour can take >ALOT of time for users to recover from!! - whether that behaviour is >considered stupid >or not, John - the truth is we all are just faking it the whole >way!) , but Ken, they >did warn us about the secure variables - weeks before the release.Only a handful of people had any idea that the variable hierarchy had been changed in version 4. The only people who knew about it were those on the BETA LIST.No one who subscribes only to this list knew about it, and they never had any method of learning about it either -- short of installing v4 and seeing their pre-existing sites break -- because that critical information never made it into the docs.There is STILL nothing in the docs to explain either the changed variable hierarchy or the no more spaces limitation in field and parameter names. Don't you think this is *critical information* they we should *ALL* be able to find in the docs? >And before a final version even came out, there was the >secure=F option. (Plus the global pref.) right?The issue here is not about the features they managed to include in the public release, the issue here is whether or not they can handle the responsibility of TELLING US ABOUT THE CHANGES THEY MADE *BEFORE* THEY BECOME PROBLEMS FOR US!The fact is, they never bothered to explain ANY of this in ANY documentation -- so how would anyone other than a handful of beta testers (and the programmers themselves) know about it? ================================ 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 Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Another new bug found ... (Nitai @ Eyework 2000)
  2. Re: Another new bug found ... (Joseph D'Andrea 2000)
  3. Re: Another new bug found ... (Nitai @ Eyework 2000)
  4. Re: Another new bug found ... (Kenneth Grome 2000)
  5. Re: Another new bug found ... (Glenn Busbin 2000)
  6. Re: Another new bug found ... (John Butler 2000)
  7. Re: Another new bug found ... (John Peacock 2000)
  8. Re: Another new bug found ... (Kenneth Grome 2000)
  9. Re: Another new bug found ... (WebDNA Support 2000)
  10. Another new bug found ... (Kenneth Grome 2000)
>agreed that an advance warning would have been nice in this case of >no spaces in >fieldnames (one perhaps small change on the side of the parser's >behaviour can take >ALOT of time for users to recover from!! - whether that behaviour is >considered stupid >or not, John - the truth is we all are just faking it the whole >way!) , but Ken, they >did warn us about the secure variables - weeks before the release.Only a handful of people had any idea that the variable hierarchy had been changed in version 4. The only people who knew about it were those on the BETA LIST.No one who subscribes only to this list knew about it, and they never had any method of learning about it either -- short of installing v4 and seeing their pre-existing sites break -- because that critical information never made it into the docs.There is STILL nothing in the docs to explain either the changed variable hierarchy or the no more spaces limitation in field and parameter names. Don't you think this is *critical information* they we should *ALL* be able to find in the docs? >And before a final version even came out, there was the >secure=F option. (Plus the global pref.) right?The issue here is not about the features they managed to include in the public release, the issue here is whether or not they can handle the responsibility of TELLING US ABOUT THE CHANGES THEY MADE *BEFORE* THEY BECOME PROBLEMS FOR US!The fact is, they never bothered to explain ANY of this in ANY documentation -- so how would anyone other than a handful of beta testers (and the programmers themselves) know about it? ================================ 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 Web Archive of this list is at: http://search.smithmicro.com/ 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:

Lambada for Macintosh is Here! (1996) Not reading code (1997) Re:trouble (1997) RE: E-mailer error codes (1997) Errata: WCS Newbie question (1997) greater than or equal to (1997) Order not created error (1997) WebCatalog can't find database (1997) Recursion & WebDNA (1999) latest version? (1998) [WebDNA] HMAC-SHA1 Encryption (2013) WC2f3 (1997) SOP for WebDNA talk - MSNBot Crashing (2004) Sorting by date (1997) relational db question (2002) [OT] Theiving B*****ds (2004) Restoring textarea stored in header (1998) Problems with ^ could be solved with [REPLACE CHARACTERS] (1997) Dr.Watson Error (1999) Multiple Items (1998)