[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: book

> From: jeremy@alum.mit.edu [mailto:jeremy@alum.mit.edu]
> This thread started with the question of whether there was a book that
> addressed the pragmatics of interpreter design.  I think Shriram is
> right to question whether the questioner really wanted a book about
> interpreters or about language implementation techniques, where
> interpretation is one possible technique.

Well, as the questioner, I think I can speak to that ;-).  The languages
I used in my youth (Pascal, C, and Fortran) were typically implemented by
making as many decisions as possible at compile time.  The languages I
used today (Python and Java) typically run on virtual machines, and
typically leave many decisions to run-time.  The distinction isn't hard
and fast --- C++ is an old-style language that makes many run-time
decisions, for example --- but most compiler courses focus on the first
family, and pay much less attention to the special needs of the second.
Gudeman's paper is a prime example of the kind of material we're missing:
you just don't worry about the run-time costs of various type encoding
schemes in C, because there is no run-time type encoding.


p.s. for those who missed it the first time around, Gudeman's paper is:

The information contained in this message is confidential and is intended 
for the addressee(s) only.  If you have received this message in error or 
there are any problems please notify the originator immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for direct, 
special, indirect or consequential damages arising from alteration of the 
contents of this message by a third party or as a result of any virus being 
passed on.

In addition, certain Marketing collateral may be added from time to time to 
promote Baltimore Technologies products, services, Global e-Security or 
appearance at trade shows and conferences.
This footnote confirms that this email message has been swept by 
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.