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 |