ANN: paxScript.NET, C# interpreter, beta version.

  • Thread starter Thread starter Alexander Baranovsky
  • Start date Start date
A

Alexander Baranovsky

Beta version of the paxScript scripting engine for the Microsoft.NET has
been released. It includes an interpreter of C# language.

www.paxscript.net

The key features of paxScript.NET are:

- paxScript.NET is written in C#. Source code of paxScript.NET is CLS
compilant.
- paxScript.NET compiles programs into byte-code. It does not use CodeDOM
and it does not generate a dynamic assembly. (paxScript.NET will generate
MSIL and executable files as an option in the future releases).
- Separate compilation of modules is allowed. You can combine source code
modules and compiled (binary) modules in your paxScript.NET project.
- C# interpreter (paxCSharp) is based on the ECMA-334 standard. It
supports all C# language features with exception for the unsafe code and
attributes. (It will support full C# 2.0 standard in the future releases).
- paxCSharp extends standard of C# language with extra features which
simplify the use of C# for scripting needs.
- paxScript.NET is implemented as a .NET component (paxscript-net.dll)
which can be used with Microsoft Visual Studio .NET, Delphi 8, Delphi 2005
and Borland C# Builder.
- Any public classes, structures, enumerations, arrays, delegates, events
and interfaces of host application can be used in a script.
- You can call script-defined methods from host application.
- Debug capabilities: breakpoints, call stack, watch/evaluate, trace into,
step over etc.

Thank you.

Alexander Baranovsky,
VIRT Laboratory
www.paxscript.com,
www.paxscript.net
 
Alexander said:
- paxScript.NET compiles programs into byte-code. It does not use CodeDOM
and it does not generate a dynamic assembly. (paxScript.NET will generate
MSIL and executable files as an option in the future releases).
Click to expand...

Sounds good, but I'm a little confused.

1) When you say "byte-code", do you compile script code into an
intermediate code that is then interpreted (in which case the byte code
is your own version of p-code)? This is an interesting approach if this
is what you're doing - I like the efficiency this might offer, along
with freedom from memory problems that often accompany dynamically
compiled assemblies.

2) Can this script language support ADO.NET (I'd like it do be able to
interact with Oracle data)?

I'm quite impressed by your projects. This shows you have a serious
ability to deal with many programming languages. This is a rare skill
among programmers...

Eric
 
Thanks for your interest.
1) When you say "byte-code", do you compile script code into an
intermediate code that is then interpreted (in which case the byte code
is your own version of p-code)? This is an interesting approach if this
is what you're doing - I like the efficiency this might offer, along
with freedom from memory problems that often accompany dynamically
compiled assemblies.
Click to expand...

Yes, paxScript.NET compiles C# code into own version of byte-code which is
represented as three-address instructions. I think this representation is
quite suitable both for code optimization (any optimization is absent in the
current version) and for conversion of paxScript.NET IL into MSIL.
2) Can this script language support ADO.NET (I'd like it do be able to
Click to expand...
interact with Oracle data)?

Certainly I'm going to provide it, but I did not test the support of ADO.NET
for now. I'll do it in the nearest days and include a few demos in the v1.0.
I'm quite impressed by your projects. This shows you have a serious
ability to deal with many programming languages. This is a rare skill
among programmers...
Click to expand...

Thank you.

A.
 
Back
Top