NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi John, I've fixed the problem, and you'll see the changes with the next release of VisAD in a few days. In the meantime, feel free to adjust the error messages yourself, since you are correct about how they were meant to be. -Curtis At 19:31 9/6/01, you wrote: >in the stringsToMethods() method of FormulaUtil, the debug statements >look like this: >System.out.println("ERROR: Class c does not exist!"); >System.out.println("ERROR: Class a[i] does not exist!"); >System.out.println("ERROR: Method m does not exist!"); > >which are not very useful. presumably, they were meant to look like >this: > >System.out.println("ERROR: Class " + c + " does not exist!"); >System.out.println("ERROR: Class " + a[i] + " does not exist!"); >System.out.println("ERROR: Method " + m + " does not exist!"); > >Sorry if this post is redundant or out of date. I'm getting back on >board with VisAD after a year and a half away from it. > >I have found that most my old code is now broken in all sorts of places >and so there's quite a bit of debugging to do. > >-john > >-- >John Brecht Software Engineer >650-859-2325(voice) Center for Technology in Learning, SRI Int'l >650-859-3673(fax) 333 Ravenswood Avenue >john.brecht@xxxxxxx Menlo Park, CA 94025
visad
archives: