<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>eagle Issue Tracker Rss Feed</title><link>http://www.codeplex.com/eagle/WorkItem/List.aspx</link><description>eagle Issue Tracker Rss Description</description><item><title>Closed Feature: optional arguments not supported [2985]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=2985</link><description>it seems that optional arguments are not supported&amp;#58;&lt;br /&gt;i.E.&lt;br /&gt;&lt;br /&gt;proc test_proc &amp;#123; &amp;#123; a 123 &amp;#125; &amp;#123; b 234 &amp;#125; &amp;#125; &amp;#123;&lt;br /&gt;   puts &amp;#34;&amp;#36;a &amp;#36;b&amp;#34;&lt;br /&gt;&amp;#125;&lt;br /&gt;throws an error when test_proc  is called without arguments&lt;br /&gt;</description><author>mistachkin</author><pubDate>Sun, 15 Nov 2009 09:45:30 GMT</pubDate><guid isPermaLink="false">Closed Feature: optional arguments not supported [2985] 20091115094530A</guid></item><item><title>Reopened Feature: optional arguments not supported [2985]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=2985</link><description>it seems that optional arguments are not supported&amp;#58;&lt;br /&gt;i.E.&lt;br /&gt;&lt;br /&gt;proc test_proc &amp;#123; &amp;#123; a 123 &amp;#125; &amp;#123; b 234 &amp;#125; &amp;#125; &amp;#123;&lt;br /&gt;   puts &amp;#34;&amp;#36;a &amp;#36;b&amp;#34;&lt;br /&gt;&amp;#125;&lt;br /&gt;throws an error when test_proc  is called without arguments&lt;br /&gt;</description><author>mistachkin</author><pubDate>Sun, 15 Nov 2009 09:45:05 GMT</pubDate><guid isPermaLink="false">Reopened Feature: optional arguments not supported [2985] 20091115094505A</guid></item><item><title>Commented Feature: optional arguments not supported [2985]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=2985</link><description>it seems that optional arguments are not supported&amp;#58;&lt;br /&gt;i.E.&lt;br /&gt;&lt;br /&gt;proc test_proc &amp;#123; &amp;#123; a 123 &amp;#125; &amp;#123; b 234 &amp;#125; &amp;#125; &amp;#123;&lt;br /&gt;   puts &amp;#34;&amp;#36;a &amp;#36;b&amp;#34;&lt;br /&gt;&amp;#125;&lt;br /&gt;throws an error when test_proc  is called without arguments&lt;br /&gt;</description><author>mistachkin</author><pubDate>Sun, 15 Nov 2009 09:45:04 GMT</pubDate><guid isPermaLink="false">Commented Feature: optional arguments not supported [2985] 20091115094504A</guid></item><item><title>Closed Feature: optional arguments not supported [2985]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=2985</link><description>it seems that optional arguments are not supported&amp;#58;&lt;br /&gt;i.E.&lt;br /&gt;&lt;br /&gt;proc test_proc &amp;#123; &amp;#123; a 123 &amp;#125; &amp;#123; b 234 &amp;#125; &amp;#125; &amp;#123;&lt;br /&gt;   puts &amp;#34;&amp;#36;a &amp;#36;b&amp;#34;&lt;br /&gt;&amp;#125;&lt;br /&gt;throws an error when test_proc  is called without arguments&lt;br /&gt;</description><author>mistachkin</author><pubDate>Sun, 15 Nov 2009 09:43:44 GMT</pubDate><guid isPermaLink="false">Closed Feature: optional arguments not supported [2985] 20091115094344A</guid></item><item><title>Commented Feature: optional arguments not supported [2985]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=2985</link><description>it seems that optional arguments are not supported&amp;#58;&lt;br /&gt;i.E.&lt;br /&gt;&lt;br /&gt;proc test_proc &amp;#123; &amp;#123; a 123 &amp;#125; &amp;#123; b 234 &amp;#125; &amp;#125; &amp;#123;&lt;br /&gt;   puts &amp;#34;&amp;#36;a &amp;#36;b&amp;#34;&lt;br /&gt;&amp;#125;&lt;br /&gt;throws an error when test_proc  is called without arguments&lt;br /&gt;</description><author>mistachkin</author><pubDate>Sun, 15 Nov 2009 09:43:31 GMT</pubDate><guid isPermaLink="false">Commented Feature: optional arguments not supported [2985] 20091115094331A</guid></item><item><title>Closed Issue: tcl load fails to load  tcl dll on Win64 [618]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=618</link><description>Attempting to use &amp;#91;tcl load&amp;#93; on Win64 with a 64bit build of tcl yields&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#37; tcl load tcl86t.dll&lt;br /&gt;Error&amp;#58; cannot delete Tcl interpreter, evals are active&lt;br /&gt;Error&amp;#58; unsuitable Tcl library, numLevels offset is not 148&lt;br /&gt;&amp;#37; exit&lt;br /&gt;&lt;br /&gt;Examining the Interp structure layout with a debugger shows that the numLevels member is at 0x98 &amp;#40;or 152 decimal&amp;#41;. So the calculation is off by 4 somewhere.&lt;br /&gt;Comments: &lt;p&gt;&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:29:46 GMT</pubDate><guid isPermaLink="false">Closed Issue: tcl load fails to load  tcl dll on Win64 [618] 20091029122946P</guid></item><item><title>Commented Issue: tcl load fails to load  tcl dll on Win64 [618]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=618</link><description>Attempting to use &amp;#91;tcl load&amp;#93; on Win64 with a 64bit build of tcl yields&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#37; tcl load tcl86t.dll&lt;br /&gt;Error&amp;#58; cannot delete Tcl interpreter, evals are active&lt;br /&gt;Error&amp;#58; unsuitable Tcl library, numLevels offset is not 148&lt;br /&gt;&amp;#37; exit&lt;br /&gt;&lt;br /&gt;Examining the Interp structure layout with a debugger shows that the numLevels member is at 0x98 &amp;#40;or 152 decimal&amp;#41;. So the calculation is off by 4 somewhere.&lt;br /&gt;Comments: ** Comment from web user: mistachkin ** &lt;p&gt;Issue cleanup, already fixed.&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:29:40 GMT</pubDate><guid isPermaLink="false">Commented Issue: tcl load fails to load  tcl dll on Win64 [618] 20091029122940P</guid></item><item><title>Closed Issue: Crash on startup on x64 [624]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=624</link><description>Wrong sizeof&amp;#40;CONTEXT&amp;#41; structure from Platform SDK header WinNT.h.&lt;br /&gt;Comments: &lt;p&gt;&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:29:09 GMT</pubDate><guid isPermaLink="false">Closed Issue: Crash on startup on x64 [624] 20091029122909P</guid></item><item><title>Commented Issue: Crash on startup on x64 [624]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=624</link><description>Wrong sizeof&amp;#40;CONTEXT&amp;#41; structure from Platform SDK header WinNT.h.&lt;br /&gt;Comments: ** Comment from web user: mistachkin ** &lt;p&gt;Issue cleanup, already fixed.&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:29:03 GMT</pubDate><guid isPermaLink="false">Commented Issue: Crash on startup on x64 [624] 20091029122903P</guid></item><item><title>Closed Task: TclTest commands (old/new style) need work [626]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=626</link><description>Complete the test and test2 commands.  Perhaps rename them to make more sense.  Create a more modular and decoupled way to run the tests and report the results.  Automatically detect if a given test needs the old or new style test command.&lt;br /&gt;Comments: &lt;p&gt;&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:28:37 GMT</pubDate><guid isPermaLink="false">Closed Task: TclTest commands (old/new style) need work [626] 20091029122837P</guid></item><item><title>Commented Task: TclTest commands (old/new style) need work [626]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=626</link><description>Complete the test and test2 commands.  Perhaps rename them to make more sense.  Create a more modular and decoupled way to run the tests and report the results.  Automatically detect if a given test needs the old or new style test command.&lt;br /&gt;Comments: ** Comment from web user: mistachkin ** &lt;p&gt;Issue cleanup, already fixed.&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:28:30 GMT</pubDate><guid isPermaLink="false">Commented Task: TclTest commands (old/new style) need work [626] 20091029122830P</guid></item><item><title>Closed Feature: Tcl stardlls do not load correctly [627]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=627</link><description>&amp;#37; tcl load &amp;#91;file join &amp;#91;pwd&amp;#93; kit-lite.dll&amp;#93;&lt;br /&gt;Error&amp;#58; Can&amp;#39;t find a usable init.tcl in the following directories&amp;#58;  ....&lt;br /&gt;&lt;br /&gt;This is due to not calling TclKit_SetKitPath.&lt;br /&gt;Also, TclKit_AppInit must be called instead of Tcl_Init when it is present.&lt;br /&gt;Comments: &lt;p&gt;&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:27:59 GMT</pubDate><guid isPermaLink="false">Closed Feature: Tcl stardlls do not load correctly [627] 20091029122759P</guid></item><item><title>Commented Feature: Tcl stardlls do not load correctly [627]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=627</link><description>&amp;#37; tcl load &amp;#91;file join &amp;#91;pwd&amp;#93; kit-lite.dll&amp;#93;&lt;br /&gt;Error&amp;#58; Can&amp;#39;t find a usable init.tcl in the following directories&amp;#58;  ....&lt;br /&gt;&lt;br /&gt;This is due to not calling TclKit_SetKitPath.&lt;br /&gt;Also, TclKit_AppInit must be called instead of Tcl_Init when it is present.&lt;br /&gt;Comments: ** Comment from web user: mistachkin ** &lt;p&gt;Issue cleanup, already fixed.&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:27:52 GMT</pubDate><guid isPermaLink="false">Commented Feature: Tcl stardlls do not load correctly [627] 20091029122752P</guid></item><item><title>Closed Issue: PE information reading functions were wrong [727]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=727</link><description>Reading the time stamp, stack reserve, and stack commit fields from the PE file was a bit more involved than I originally thought.  The offsets must be based on another offset found at a fixed offset.&lt;br /&gt;&lt;br /&gt;This has been fixed and the code has also been made to check the header signatures now.&lt;br /&gt;Comments: &lt;p&gt;&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:27:06 GMT</pubDate><guid isPermaLink="false">Closed Issue: PE information reading functions were wrong [727] 20091029122706P</guid></item><item><title>Commented Issue: PE information reading functions were wrong [727]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=727</link><description>Reading the time stamp, stack reserve, and stack commit fields from the PE file was a bit more involved than I originally thought.  The offsets must be based on another offset found at a fixed offset.&lt;br /&gt;&lt;br /&gt;This has been fixed and the code has also been made to check the header signatures now.&lt;br /&gt;Comments: ** Comment from web user: mistachkin ** &lt;p&gt;Issue cleanup, already fixed.&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:26:58 GMT</pubDate><guid isPermaLink="false">Commented Issue: PE information reading functions were wrong [727] 20091029122658P</guid></item><item><title>Closed Task: Benchmark/profile performance and optimize [841]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=841</link><description>The script parser, engine, and several commands need performance tuning.&lt;br /&gt;&lt;br /&gt;1. Create a standard set of test scripts to act as a benchmark for any performance improvements.&lt;br /&gt;2. Run the benchmarks with and without profiling.&lt;br /&gt;3. Surgically optimize.&lt;br /&gt;4. Rinse and repeat.&lt;br /&gt;Comments: &lt;p&gt;&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:26:21 GMT</pubDate><guid isPermaLink="false">Closed Task: Benchmark/profile performance and optimize [841] 20091029122621P</guid></item><item><title>Commented Task: Benchmark/profile performance and optimize [841]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=841</link><description>The script parser, engine, and several commands need performance tuning.&lt;br /&gt;&lt;br /&gt;1. Create a standard set of test scripts to act as a benchmark for any performance improvements.&lt;br /&gt;2. Run the benchmarks with and without profiling.&lt;br /&gt;3. Surgically optimize.&lt;br /&gt;4. Rinse and repeat.&lt;br /&gt;Comments: ** Comment from web user: mistachkin ** &lt;p&gt;Issue cleanup, already fixed.&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:26:14 GMT</pubDate><guid isPermaLink="false">Commented Task: Benchmark/profile performance and optimize [841] 20091029122614P</guid></item><item><title>Closed Issue: Traces do not fire for variables created via upvar [1022]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=1022</link><description>The wrong constructor overload was being used to create Variable objects from an upvar operation.&lt;br /&gt;Comments: &lt;p&gt;&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:25:31 GMT</pubDate><guid isPermaLink="false">Closed Issue: Traces do not fire for variables created via upvar [1022] 20091029122531P</guid></item><item><title>Commented Issue: Traces do not fire for variables created via upvar [1022]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=1022</link><description>The wrong constructor overload was being used to create Variable objects from an upvar operation.&lt;br /&gt;Comments: ** Comment from web user: mistachkin ** &lt;p&gt;Issue cleanup, already fixed.&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:25:26 GMT</pubDate><guid isPermaLink="false">Commented Issue: Traces do not fire for variables created via upvar [1022] 20091029122526P</guid></item><item><title>Closed Issue: interpreter host can get out of sync with debugger interpreter host [1264]</title><link>http://eagle.codeplex.com/WorkItem/View.aspx?WorkItemId=1264</link><description>if a caller sets the interpreter host, it may get out of sync with the host for the interpreter of the contained debugger &amp;#40;if any&amp;#41;.&lt;br /&gt;Comments: &lt;p&gt;&lt;/p&gt;</description><author>mistachkin</author><pubDate>Thu, 29 Oct 2009 12:25:02 GMT</pubDate><guid isPermaLink="false">Closed Issue: interpreter host can get out of sync with debugger interpreter host [1264] 20091029122502P</guid></item></channel></rss>