Re: debuging and getting mor information about failures

>These errors are usually caused by an extra or missing brace or >quote/apostrophe/backtick. The best way to find where this is happening >is to use another error. Alternatively, use a text editor that's syntax-aware. In bbedit for the mac, finishing a closure or double-clicking on one (parens, brackets, braces, etc.) shows you the beginning and end in an unobtrusive way. Finishing a closure that was not open (too many close parens) causes a system beep. The hints are subtle, but help you codee correctly as you go. I think Ultraedit is a good alternative for the pc. --------------------------------------------------------------------- michal migurski- contact info and pgp key: sf/ca http://mike.teczno.com/contact.html