Re: Scripting language interfaces

"Martin Bertolino" <>
3 Apr 1998 17:14:54 -0500

          From comp.compilers

Related articles
Scripting language interfaces (Steve Atkins) (1998-03-24)
Re: Scripting language interfaces (1998-03-30)
Re: Scripting language interfaces (1998-03-30)
Re: Scripting language interfaces (Roland Kaufmann) (1998-04-03)
Re: Scripting language interfaces (Martin Bertolino) (1998-04-03)
| List of all articles for this month |

From: "Martin Bertolino" <>
Newsgroups: comp.compilers
Date: 3 Apr 1998 17:14:54 -0500
Organization: CRL Network Services
References: 98-03-223 98-03-258
Keywords: interpreter

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
execute ASP. There are two engines published by MS, JavaScript and
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.

Martin Bertolino

Sebastiano Pilla wrote...
>> Has anyone seen any work on a standard API for scripting languages?

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.