Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!agate!ucbvax!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!charon!guido
From: guido@cwi.nl (Guido van Rossum)
Newsgroups: comp.arch
Subject: Re: Compilers and efficiency
Message-ID: <3311@charon.cwi.nl>
Date: 13 Apr 91 12:05:30 GMT
References: <10205@mentor.cc.purdue.edu>
Sender: news@cwi.nl
Lines: 11

hrubin@pop.stat.purdue.edu (Herman Rubin) writes:

>[...]  An adequate macro processor would
>include the capability of easily translating APL into other languages,
>for example, and even having the translation take into account types.

Can you give some more clues that this statement is true?  Without any
more context it sounds like what you call a macro processor is
something completely different from what is usually called a macro
processor; for instance, normally macro processors have no notion
whatsoever of the types they are working on.