Eagle

Project License Changed

Fri, 06 Nov 2009 07:17:54 GMT

Copyright (c) 2007-2009, Joe Mistachkin All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of The Eagle Project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Updated Release: Beta 1.0.3596.38043 (Nov 05, 2009)

mistachkin — Fri, 06 Nov 2009 07:07:50 GMT

Eagle (Extensible Adaptable Generalized Logic Engine) is an implementation of the Tcl scripting language for the Common Language Runtime (CLR). It is designed to be a universal scripting solution for any CLR-based language.

This is the Eagle 1.0 beta distribution.

Contents

1. Introduction
2. Documentation
3. Compiling and Installing Eagle

1. Introduction

Eagle (Extensible Adaptable Generalized Logic Engine) is an implementation of
the Tcl scripting language for the Common Language Runtime (CLR). It is
designed to be a universal scripting solution for any CLR-based language. It
is written completely in C#. Superficially, it is similar to Jacl; however, it
was written from scratch based on the design and implementation of Tcl 8.4. It
provides most of the functionality of the Tcl 8.4 interpreter while borrowing
selected features from Tcl 8.5 and the upcoming Tcl 8.6 in addition to adding
entirely new features.

Eagle is maintained, enhanced, and distributed freely by the Eagle community
(which may have some degree of cross-membership with the Tcl community). The
home for the Eagle sources and the bug/patch database is on CodePlex:

http://eagle.codeplex.com/

with the Eagle web site hosted at:

http://eagle.to/

Eagle is a freely available open source package. You can do virtually anything
you like with it, such as modifying it, redistributing it, and selling it
either in whole or in part. See the file "license.terms" for complete
information.

2. Documentation

The documentation for Tcl 8.4 script commands and syntax largely applies to
Eagle as well. Additional documentation is a work in progress.

This includes:

A. The Tcl commands missing from Eagle.
B. The differences between Tcl and Eagle commands, where applicable.
C. The Eagle commands that have no Tcl equivalent.
D. The managed integration and extensibility APIs.

3. Compiling and Installing Eagle

Prior to compiling and running Eagle, you should run the provided Strong Name
Verification Skipping Tool (i.e. "Library\Tools\strongName.bat" or
"Library\Tools\strongName.reg"). This is necessary because [for security
reasons] the official strong name signing private keys are not part of the
public source distribution. Alternatively, you may choose to sign the
assemblies with the strong name signing key of your choice.

The sources may be built from inside the Microsoft Visual Studio 2005 (or
higher) integrated development environment. Alternatively, they may be built
using the Microsoft .NET Framework Version 2.0 RTM (or higher) command line
build environment.

To build for the Windows platform, use the following command:

MSBuild Eagle.sln /t:Rebuild

To build for the Unix platform, use the following command:

MSBuild Eagle.sln /t:Rebuild /p:EagleWindows=false /p:EagleUnix=true

To build and run the test suite, use the following command:

MSBuild Eagle.sln /t:Rebuild /p:EagleRunTests=true

There are a variety of other compile time options that may be specified when
building from the command line. For example, to disable features which are
known not to work correctly in Mono 2.0, add "/p:EagleMono=true" to either of
the command lines above. Please refer to the file "Eagle.Settings.targets" for
more information.

Released: Beta 1.0.3596.38043 (Nov 05, 2009)

Fri, 06 Nov 2009 07:07:50 GMT

Contents

1. Introduction
2. Documentation
3. Compiling and Installing Eagle

Closed Issue: tcl load fails to load tcl dll on Win64 [618]

mistachkin — Thu, 29 Oct 2009 12:29:46 GMT

Attempting to use [tcl load] on Win64 with a 64bit build of tcl yields:

% tcl load tcl86t.dll
Error: cannot delete Tcl interpreter, evals are active
Error: unsuitable Tcl library, numLevels offset is not 148
% exit

Examining the Interp structure layout with a debugger shows that the numLevels member is at 0x98 (or 152 decimal). So the calculation is off by 4 somewhere.
Comments:

Commented Issue: tcl load fails to load tcl dll on Win64 [618]

mistachkin — Thu, 29 Oct 2009 12:29:40 GMT

Issue cleanup, already fixed.

Closed Issue: Crash on startup on x64 [624]

mistachkin — Thu, 29 Oct 2009 12:29:09 GMT

Wrong sizeof(CONTEXT) structure from Platform SDK header WinNT.h.
Comments:

Commented Issue: Crash on startup on x64 [624]

mistachkin — Thu, 29 Oct 2009 12:29:03 GMT

Wrong sizeof(CONTEXT) structure from Platform SDK header WinNT.h.
Comments: ** Comment from web user: mistachkin **

Issue cleanup, already fixed.

Closed Task: TclTest commands (old/new style) need work [626]

mistachkin — Thu, 29 Oct 2009 12:28:37 GMT

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.
Comments:

Commented Task: TclTest commands (old/new style) need work [626]

mistachkin — Thu, 29 Oct 2009 12:28:30 GMT

Issue cleanup, already fixed.

Closed Feature: Tcl stardlls do not load correctly [627]

mistachkin — Thu, 29 Oct 2009 12:27:59 GMT

% tcl load [file join [pwd] kit-lite.dll]
Error: Can't find a usable init.tcl in the following directories: ....

This is due to not calling TclKit_SetKitPath.
Also, TclKit_AppInit must be called instead of Tcl_Init when it is present.
Comments:

Commented Feature: Tcl stardlls do not load correctly [627]

mistachkin — Thu, 29 Oct 2009 12:27:52 GMT

Issue cleanup, already fixed.

Closed Issue: PE information reading functions were wrong [727]

mistachkin — Thu, 29 Oct 2009 12:27:06 GMT

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.

This has been fixed and the code has also been made to check the header signatures now.
Comments:

Commented Issue: PE information reading functions were wrong [727]

mistachkin — Thu, 29 Oct 2009 12:26:58 GMT

Issue cleanup, already fixed.

Closed Task: Benchmark/profile performance and optimize [841]

mistachkin — Thu, 29 Oct 2009 12:26:21 GMT

The script parser, engine, and several commands need performance tuning.

1. Create a standard set of test scripts to act as a benchmark for any performance improvements.
2. Run the benchmarks with and without profiling.
3. Surgically optimize.
4. Rinse and repeat.
Comments:

Commented Task: Benchmark/profile performance and optimize [841]

mistachkin — Thu, 29 Oct 2009 12:26:14 GMT

Issue cleanup, already fixed.

Closed Issue: Traces do not fire for variables created via upvar [1022]

mistachkin — Thu, 29 Oct 2009 12:25:31 GMT

The wrong constructor overload was being used to create Variable objects from an upvar operation.
Comments:

Commented Issue: Traces do not fire for variables created via upvar [1022]

mistachkin — Thu, 29 Oct 2009 12:25:26 GMT

The wrong constructor overload was being used to create Variable objects from an upvar operation.
Comments: ** Comment from web user: mistachkin **

Issue cleanup, already fixed.

Closed Issue: interpreter host can get out of sync with debugger interpreter host [1264]

mistachkin — Thu, 29 Oct 2009 12:25:02 GMT

if a caller sets the interpreter host, it may get out of sync with the host for the interpreter of the contained debugger (if any).
Comments:

Commented Issue: interpreter host can get out of sync with debugger interpreter host [1264]

mistachkin — Thu, 29 Oct 2009 12:24:56 GMT

if a caller sets the interpreter host, it may get out of sync with the host for the interpreter of the contained debugger (if any).
Comments: ** Comment from web user: mistachkin **

Issue cleanup, already fixed.

Closed Issue: Interactive loop handling of break-on-cancel not correct [1265]

mistachkin — Thu, 29 Oct 2009 12:24:19 GMT

the interactive loop did not take into account break-on-cancel when checking whether the previous input should have been considered as canceled.
Comments: