Newsgroups: gnu.misc.discuss,comp.lang.tcl,comp.lang.scheme,comp.lang.misc,comp.lang.perl
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!news.duke.edu!news-feed-1.peachnet.edu!gatech!swrinde!news.uh.edu!uuneo.neosoft.com!nmtigw!peter
From: peter@nmti.com (Peter da Silva)
Subject: Re: GNU Extension Language Plans
Message-ID: <id.HH4E1.XL2@nmti.com>
Sender: peter@nmti.com (peter da silva)
Organization: Network/development platform support, NMTI
References: <9410190420.AA02904@mole.gnu.ai.mit.edu> <38ftvn$d4a@nntp1.u.washington.edu> <id.Y44E1.KLF@nmti.com> <ROCKWELL.94Oct24132137@nova.umd.edu>
Date: Mon, 24 Oct 1994 22:38:35 GMT
Lines: 22
Xref: glinda.oz.cs.cmu.edu gnu.misc.discuss:19126 comp.lang.tcl:20852 comp.lang.scheme:10582 comp.lang.misc:18380 comp.lang.perl:37024

In article <ROCKWELL.94Oct24132137@nova.umd.edu>,
Raul Deluth Miller <rockwell@nova.umd.edu> wrote:
> Peter da Silva:
> . Now, if you're using an external compiler you need to run that compiler
> . from "define_key_macro".

> Depending on the definition of define_key_macro.  [Some definitions
> of define_key_macro wouldn't expose any of the details of the
> extension language.]

I'm sorry, you've lost me. Either the extension language the user's
interested in is built into the executable, in which case they all
have to be, or it's got to be execed to convert the user's key macro
string into the implementation language, which gives you too much
of a performance hit, or you expose the underlying mechanics of the
implementation language to the user, which is what I thought you were
trying to avoid. What's the fourth alternative?
-- 
Peter da Silva                                            `-_-'
Network Management Technology Incorporated                 'U`
1601 Industrial Blvd.     Sugar Land, TX  77478  USA
+1 713 274 5180                       "Hast Du heute schon Deinen Wolf umarmt?"
