Re: Scripting Languages (was Re: Techniques for writing an interpreter)

bmcsweeney@bigfoot.com
30 Mar 1998 21:42:15 -0500

          From comp.compilers

Related articles
[6 earlier articles]
Re: Techniques for writing an interpreter a010111t@bc.seflin.org (Orlando Llanes) (1998-03-20)
Scripting Languages (was Re: Techniques for writing an interpreter) creedy@mitretek.org (Chris Reedy) (1998-03-24)
Re: Scripting Languages (was Re: Techniques for writing an interpreter markh@usai.asiainfo.com (Mark Harrison) (1998-03-30)
Re: Scripting Languages (was Re: Techniques for writing an interpreter tiggr@ics.ele.tue.nl (1998-03-30)
Scripting Languages (was Re: Techniques for writing an interpreter) jhonan@mpx.com.au (1998-03-30)
Re: Scripting Languages (was Re: Techniques for writing an interpreter hgg9140@heckle.ca.boeing.com (1998-03-30)
Re: Scripting Languages (was Re: Techniques for writing an interpreter bmcsweeney@bigfoot.com (1998-03-30)
Re: Scripting Languages (was Re: Techniques for writing an interpreter cgregg@dsp.sps.mot.com (Chris Gregg) (1998-03-30)
| List of all articles for this month |

From: bmcsweeney@bigfoot.com
Newsgroups: comp.compilers
Date: 30 Mar 1998 21:42:15 -0500
Organization: Deja News - The Leader in Internet Discussion
References: 98-03-032 98-03-098 98-03-141 98-03-147 98-03-159 98-03-186 98-03-201 98-03-233
Keywords: interpreter

    Chris Reedy <creedy@mitretek.org> wrote:
[snipped]
> A quick question: What are the key differences between a scripting
> language and an ordinary programming language? That is, what is it
> about a language that makes it better or worse for the uses described
> above?


Briefly, a scripting language would most likely be embedded within a
larger application and provide a user interface which would be
programmable and allow the user/programmer access to the "engine" of
the application in order to make it more responsive.


/s/ brianm.
--


Post a followup to this message

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