RE: JESS: trying to save a bad CLP file crashes JessDE
It has happened to me. It is pretty random when it occurs, but I have experienced eclipse hanging on a save for a .clp file. When I restart eclipse, the changes were saved so it is more of a annoyance. Scott L. Krasnigor Sr. Principal Engineer/Scientist Advanced Sciences Technologies, LLC. Lockheed Martin - MS2 ' 856-359-3094 * [EMAIL PROTECTED] * 780-3 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Morris Sent: Tuesday, May 22, 2007 4:49 AM To: jess-users@sandia.gov Subject: JESS: trying to save a bad CLP file crashes JessDE Hi Ernest, When I try to save a CLP file that is in a bad state (not parsing correctly) JessDE has a pesky propensity to lockup and take down Eclipse (on my box admittedly) in both 3.2 and 3.2.2 versions. Version 3.2.2 was worse. I'm 99% sure it's not the code itself that's doing it. Take any valid CLP file of moderate size, whack a ) or two out, let the parser gag, then try to save and see what happens. I would expect JessDE to have the same behavior as Eclipse when editing a bad java file -- it's not a problem to save it in that state. Now before you say, Uh, fix the bug first and THEN save let me say that one of the habits that I've gotten into is to immediately hit Ctrl+S (Save) whenever: a) I stop coding to take a break or reflect. b) Something unexpected happens in my code while coding. c) Any other error happens that doesn't crash the IDE I'm using at the time. This habit has saved me thousands of lines of code, so I'm reluctant to change it. :-) This brings up a few things: 1) Has this happened to anyone else? Can anyone reproduce this phenomenon? (I'll give Ernest the benefit of the doubt, of course). 2) Is there a practical size limit to a CLP file beyond which one should, as a best practice, break it into smaller files (i.e, by modules)? 3) Is there a way (or should there be if not) to suspend JessDE parsing and treat it more like validation which you can toggle on and off? Cheers, Jason --- Jason C. Morris Worcester Polytechnic Institute Phone: (508) 831-5006 Department of Computer Science FAX: (508) 831-5776 Fuller Laboratories - Room 312 [EMAIL PROTECTED] Artificial Intelligence Lab (AIRG) 100 Institute Road Worcester, MA 01609-2280 ---
Re: JESS: trying to save a bad CLP file crashes JessDE
Hi Scott, It has happened to me. It is pretty random when it occurs Exactly! OK, so I'm not the only one :-) And yes, I've had Eclipse just hang on trying to save a CLP without there being any parse errors present, too. Cheers, Jason On 5/22/07, Krasnigor, Scott L (N-AST) [EMAIL PROTECTED] wrote: It has happened to me. It is pretty random when it occurs, but I have experienced eclipse hanging on a save for a .clp file. When I restart eclipse, the changes were saved so it is more of a annoyance. *Scott L. Krasnigor* Sr. Principal Engineer/Scientist Advanced Sciences Technologies, LLC. Lockheed Martin - MS2 ' 856-359-3094 ** [EMAIL PROTECTED] * 780-3 -- *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Jason Morris *Sent:* Tuesday, May 22, 2007 4:49 AM *To:* jess-users@sandia.gov *Subject:* JESS: trying to save a bad CLP file crashes JessDE Hi Ernest, When I try to save a CLP file that is in a bad state (not parsing correctly) JessDE has a pesky propensity to lockup and take down Eclipse (on my box admittedly) in both 3.2 and 3.2.2 versions. Version 3.2.2 was worse. I'm 99% sure it's not the code itself that's doing it. Take any valid CLP file of moderate size, whack a ) or two out, let the parser gag, then try to save and see what happens. I would expect JessDE to have the same behavior as Eclipse when editing a bad java file -- it's not a problem to save it in that state. Now before you say, Uh, fix the bug first and THEN save let me say that one of the habits that I've gotten into is to immediately hit Ctrl+S (Save) whenever: a) I stop coding to take a break or reflect. b) Something unexpected happens in my code while coding. c) Any other error happens that doesn't crash the IDE I'm using at the time. This habit has saved me thousands of lines of code, so I'm reluctant to change it. :-) This brings up a few things: 1) Has this happened to anyone else? Can anyone reproduce this phenomenon? (I'll give Ernest the benefit of the doubt, of course). 2) Is there a practical size limit to a CLP file beyond which one should, as a best practice, break it into smaller files (i.e, by modules)? 3) Is there a way (or should there be if not) to suspend JessDE parsing and treat it more like validation which you can toggle on and off? Cheers, Jason --- Jason C. Morris Worcester Polytechnic Institute Phone: (508) 831-5006 Department of Computer Science FAX: (508) 831-5776 Fuller Laboratories - Room 312 [EMAIL PROTECTED] Artificial Intelligence Lab (AIRG) 100 Institute Road Worcester, MA 01609-2280 --- -- --- Jason C. Morris Worcester Polytechnic Institute Phone: (508) 831-5006 Department of Computer Science FAX: (508) 831-5776 Fuller Laboratories - Room 312 [EMAIL PROTECTED] Artificial Intelligence Lab (AIRG) 100 Institute Road Worcester, MA 01609-2280 ---
Re: JESS: trying to save a bad CLP file crashes JessDE
On May 22, 2007, at 4:49 AM, Jason Morris wrote: Hi Ernest, When I try to save a CLP file that is in a bad state (not parsing correctly) JessDE has a pesky propensity to lockup and take down Eclipse (on my box admittedly) in both 3.2 and 3.2.2 versions. I just spent a few minutes trying to replicate this, but I could not. How large is moderate? Maybe there's a particular feature that must be used in the file? Can somebody provide me with a file which triggers this? - Ernest Friedman-Hill Advanced Software Research Phone: (925) 294-2154 Sandia National LabsFAX: (925) 294-2234 PO Box 969, MS 9012 [EMAIL PROTECTED] Livermore, CA 94550 http://www.jessrules.com To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED]
