|Scripting language interfaces email@example.com (Steve Atkins) (1998-03-24)|
|Re: Scripting language interfaces firstname.lastname@example.org (1998-03-30)|
|Re: Scripting language interfaces email@example.com (1998-03-30)|
|Re: Scripting language interfaces firstname.lastname@example.org (Roland Kaufmann) (1998-04-03)|
|Re: Scripting language interfaces email@example.com (Martin Bertolino) (1998-04-03)|
|From:||Steve Atkins <firstname.lastname@example.org>|
|Date:||24 Mar 1998 22:42:44 -0500|
|Organization:||Digital Equipment Corporation, Palo Alto, CA, USA|
|Keywords:||interpreter, design, question|
Some people like scheme, some prefer tcl, others visual basic, and yet
It would be nice if the enduser could take its favourite scripting
language plugin, add it to its new application and have everything
work. It would save the 'which scripting language do we use?'
decisions for application developers.
Has anyone seen any work on a standard API for scripting languages?
The only things I've seen that's close is the microsoft activex
scripting engine interface, and some early discussion of guile
providing multiple languages to the end-user.
I'd hate to re-invent the wheel again.
-- Steve Atkins -- email@example.com
Return to the
Search the comp.compilers archives again.