From: <no...@so...> - 2000-11-30 18:25:15
|
Bug #123973, was updated on 2000-Nov-30 10:25 Here is a current snapshot of the bug. Project: Tcl Category: Commands Status: Open Resolution: None Bug Group: None Priority: 5 Summary: jacl1.2.6 info complete Details: The test suite reports problems with the info complete command. One is easy to fix. Any comment not terminated in a newline is considered incomplete, e.g. info complete "#" returns 0, info complete "#\n" returns 1. Looking at the 8.2.3 C version the following corrects this: Parser.java: 158c158 < parse.incomplete = true; --- > if (nested) parse.incomplete = true; The second is more difficult. It seems that in parsing an info complete command the first character after a ';' is lost so that info complete ";#{" returns 0, info complete "; #{" returns 1. Examing script_index and cur at the top of the first while loop in parseCommand bears this out. This doesn't occur during normal parsing or an eval. The 8.2.3 C version doesn't have this problem. Dave Heisterberg For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=123973&group_id=10894 |
From: <no...@so...> - 2001-02-07 16:01:25
|
Bug #123973, was updated on 2000-Nov-30 10:25 Here is a current snapshot of the bug. Project: Tcl Category: Commands I-L Status: Open Resolution: None Bug Group: None Priority: 5 Submitted by: djh26cas Assigned to : nobody Summary: jacl1.2.6 info complete Details: The test suite reports problems with the info complete command. One is easy to fix. Any comment not terminated in a newline is considered incomplete, e.g. info complete "#" returns 0, info complete "#\n" returns 1. Looking at the 8.2.3 C version the following corrects this: Parser.java: 158c158 < parse.incomplete = true; --- > if (nested) parse.incomplete = true; The second is more difficult. It seems that in parsing an info complete command the first character after a ';' is lost so that info complete ";#{" returns 0, info complete "; #{" returns 1. Examing script_index and cur at the top of the first while loop in parseCommand bears this out. This doesn't occur during normal parsing or an eval. The 8.2.3 C version doesn't have this problem. Dave Heisterberg For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=123973&group_id=10894 |
From: <no...@so...> - 2001-02-07 17:49:55
|
Bug #123973, was updated on 2000-Nov-30 10:25 Here is a current snapshot of the bug. Project: Tcl Category: Commands I-L Status: Closed Resolution: Invalid Bug Group: None Priority: 5 Submitted by: djh26cas Assigned to : mdejong Summary: jacl1.2.6 info complete Details: The test suite reports problems with the info complete command. One is easy to fix. Any comment not terminated in a newline is considered incomplete, e.g. info complete "#" returns 0, info complete "#\n" returns 1. Looking at the 8.2.3 C version the following corrects this: Parser.java: 158c158 < parse.incomplete = true; --- > if (nested) parse.incomplete = true; The second is more difficult. It seems that in parsing an info complete command the first character after a ';' is lost so that info complete ";#{" returns 0, info complete "; #{" returns 1. Examing script_index and cur at the top of the first while loop in parseCommand bears this out. This doesn't occur during normal parsing or an eval. The 8.2.3 C version doesn't have this problem. Dave Heisterberg Follow-Ups: Date: 2001-Feb-07 09:50 By: dgp Comment: This bug report is meant for Jacl, not Tcl. I've marked it invalid and closed it. It should be reassigned the the Tcl/Java project. Mo, since you admin both projects, I assume you can re-assign and re-open this bug in the right place? ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=123973&group_id=10894 |
From: <no...@so...> - 2001-02-07 21:53:44
|
Bug #123973, was updated on 2000-Nov-30 10:25 Here is a current snapshot of the bug. Project: Tcl/Java Category: None Status: Closed Resolution: Invalid Bug Group: None Priority: 5 Submitted by: djh26cas Assigned to : nobody Summary: jacl1.2.6 info complete Details: The test suite reports problems with the info complete command. One is easy to fix. Any comment not terminated in a newline is considered incomplete, e.g. info complete "#" returns 0, info complete "#\n" returns 1. Looking at the 8.2.3 C version the following corrects this: Parser.java: 158c158 < parse.incomplete = true; --- > if (nested) parse.incomplete = true; The second is more difficult. It seems that in parsing an info complete command the first character after a ';' is lost so that info complete ";#{" returns 0, info complete "; #{" returns 1. Examing script_index and cur at the top of the first while loop in parseCommand bears this out. This doesn't occur during normal parsing or an eval. The 8.2.3 C version doesn't have this problem. Dave Heisterberg Follow-Ups: Date: 2001-Feb-07 13:54 By: mdejong Comment: Moving to Tcl/Java project. ------------------------------------------------------- Date: 2001-Feb-07 09:50 By: dgp Comment: This bug report is meant for Jacl, not Tcl. I've marked it invalid and closed it. It should be reassigned the the Tcl/Java project. Mo, since you admin both projects, I assume you can re-assign and re-open this bug in the right place? ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=123973&group_id=13005 |