Envelope-to: eclipse-bugs@icparc.ic.ac.uk Delivery-date: Fri, 5 Apr 2002 15:19:46 +0100 From: Stefano Novello <stefano.novello@parc-technologies.com> Date: Fri, 5 Apr 2002 15:20:51 +0100 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1DCAD.16B83B30" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1DCAD.16B83B30 Content-Type: text/plain; charset="iso-8859-1" Hello, When writing a term from Java, if the term has been badly constructed and does not only contain EclipeTerms Strings and Numbers an exception is thrown. This exception just says a wrong type was encountered. Could we mention the class name in the message? I've added it to the 5.3 patch branch. It would then be easier to track down such a bug. Currently this can be quite hard if you are writing out a large term. We could also catch this early when constructing the EclipseTermImpl as well. The problem with trying to catch it early is that the constructors for CompoundTerms can take arbitrary Collections which may be added to after the term has been constructed. However, you should be able to use a tool like JProbe or OptimizeIt to tell you where in the code the offending object was constructed. Andrew (Sadler) Stefano 2nd Floor The Tower Building EMAIL: Stefano.Novello@parc-technologies.com 11 York Road TEL: +44 (0)20 72614068 SE1 7NX LONDONReceived on Fri Apr 05 16:27:37 2002
This archive was generated by hypermail 2.1.8 : Wed 16 Nov 2005 06:08:14 PM GMT GMT