|Usability advice to compiler/interpreter authors claird@Starbase.NeoSoft.COM (1995-08-14)|
|Re: Usability advice to compiler/interpreter authors email@example.com (1995-08-17)|
|From:||claird@Starbase.NeoSoft.COM (Cameron Laird)|
|Organization:||NeoSoft Internet Services +1 713 968 5800|
|Date:||Mon, 14 Aug 1995 04:13:49 GMT|
Compiler/interpreter authors, please give us users analysis-time
access to version, platform, and invocation data (especially the
first of these). I'll illustrate with an example: a C compiler
should always insert some default values in its table of manifest
constants, so that developers can write
Analogous facilities would help particular instance of Scheme, BASIC,
... interpreters and FORTRAN, Ada, ... compilers.
I don't have any interesting theory to accompany this plea; I
don't think there's a single intellectually profound problem this
solves. However, facilities like this make an enormous difference
to us working developers out in the real world.
Cameron Laird http://starbase.neosoft.com/~claird/home.html
claird@Neosoft.com +1 713 267 7966
firstname.lastname@example.org +1 713 996 8546 FAX
[A counter theory decries bushy ifdefs as making reliable code much harder
to write. I have sympathy for both camps. -John]
Return to the
Search the comp.compilers archives again.