|Scripting language interfaces firstname.lastname@example.org (Steve Atkins) (1998-03-24)|
|Re: Scripting language interfaces email@example.com (1998-03-30)|
|Re: Scripting language interfaces firstname.lastname@example.org (1998-03-30)|
|Re: Scripting language interfaces email@example.com (Roland Kaufmann) (1998-04-03)|
|Re: Scripting language interfaces firstname.lastname@example.org (Martin Bertolino) (1998-04-03)|
|From:||"Martin Bertolino" <email@example.com>|
|Date:||3 Apr 1998 17:14:54 -0500|
|Organization:||CRL Network Services|
Another approach you might want to take a look at is Miscrosoft's
Active Scripting Engines. The main idea is to expose the Scripting
Engine to your application throught a 2 COM interfaces. Likewise your
application as accessible from the scripting language by implementing
2 COM interfaces and representing the objects of your application with
COM components and interfaces. This is a Microsoft Standard and it
relies on COM so you are limited to Micorosft operating systems or
platforms with COM support. I have used in one project and it works
very well. This technology is also used by Internet Explorer to parse
and interpret the <SCRIPT> tags in an HTML document, and by IIS to
VBScript. There is also a Perl engine from the people that produce
Perl for Windows platforms. You can fin more information at:
Understanding ActiveX and COM, Davis Chappell, MSPRESS
If you don't have a problem making your project dependent on MS products you
might find this useful.
Sebastiano Pilla wrote...
>> Has anyone seen any work on a standard API for scripting languages?
Return to the
Search the comp.compilers archives again.