ANN: paxScript, v2.6
From: Alexander Baranovsky (ab_at_cable.netlux.org)
Date: 11/27/04
- Next message: Dennis Landi: "Re: paxScript, v2.6"
- Previous message: QHenrick_Hellstr=F6m_=5BStreamSec=5D=22?=: "Re: Weather Information?"
- Next in thread: Dennis Landi: "Re: paxScript, v2.6"
- Reply: Dennis Landi: "Re: paxScript, v2.6"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 27 Nov 2004 17:33:55 +0200
New version of the paxScript scripting engine has been released.
Major changes in v2.6:
. Importing interface types.
. Operator overloading in paxJavaScript.
The key features of the paxScript are:
- paxScript supports 4 scripting languages: paxPascal, paxBasic, paxC and
paxJavaScript..
- All pax-languages support such concepts of the modern programming as
namespaces, nested classes, inheritance, static(shared) members, indexed
properties, default parameters, overloaded routines, operator overloading,
delegates, exception handling, regular expressions, conditional compilation,
included files.
- Cross-language programming. For example, you can use modules written in
paxBasic and paxC in your paxPascal scripts and vice versa.
- Separate compilation of the modules.
- Direct calling of dll-defined routines. All calling conventions register,
pascal, cdecl, stdcall, safecall are supported.
- Embedding scripts into html pages.
All paxScript languages support LISPPA technology which considerably extends
the applicability of imperative programming languages in the symbolic
computations and AI applications.
TPaxScripter component allows you to embed the paxScript interpreter into
your Delphi, Kylix or Borland C++ Builder application, so you can extend and
customize the application without having to recompile it.
Using TPaxScripter you can
- Import Delphi classes routines, constants, and variables.
- Import Delphi units automatically with paxScript importer.
- Convert dfm-files into the paxPascal scripts.
- Call script-defined functions.
- Save/load compiled scripts to/from a stream.
- Unite source code modules and compiled (binary) modules in your script
project. Moreover, you can add full compiled script to the script project.
- Build the code explorer tree.
- Customize compilation process and error handling.
- Use scripter in the debugger mode (breakpoints, watches, call stack, step
into, trace over, run to cursor). The component comes with full source code
of paxScript IDE, so you can use it as a base for developing your own
integrated environment.
Source code of the paxScript interpreter and TPaxScripter component is
written entirely with Delphi and compatible with Delphi 5, Delphi 6,
Delphi 7, C++ Builder 5, C++ Builder 6, Kylix 3. You don't need any extra
DLLs or OCXs.
TPaxScripter component is thread safe. It has small footprint (about 30-40
Kb per extra TPaxScripter instance).
Thank you.
Alexander Baranovsky,
VIRT Laboratory
www.paxscript.com
ab@cable.netlux.org
- Next message: Dennis Landi: "Re: paxScript, v2.6"
- Previous message: QHenrick_Hellstr=F6m_=5BStreamSec=5D=22?=: "Re: Weather Information?"
- Next in thread: Dennis Landi: "Re: paxScript, v2.6"
- Reply: Dennis Landi: "Re: paxScript, v2.6"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
