Related articles |
---|
[8 earlier articles] |
Re: Basic-Like PCODE Compiler and Virtual Host/Interpreter kenrose@tfb.com (Ken Rose) (2004-04-28) |
Re: Basic-Like PCODE Compiler and Virtual Host/Interpreter freitag@alancoxonachip.com (Andi Kleen) (2004-04-28) |
Re: Basic-Like PCODE Compiler and Virtual Host/Interpreter arargh404@NOW.AT.arargh.com (2004-04-29) |
Re: Basic-Like PCODE Compiler and Virtual Host/Interpreter alex_mcd@btopenworld.com (Alex McDonald) (2004-05-02) |
Re: Basic-Like PCODE Compiler and Virtual Host/Interpreter thp@cs.ucr.edu (2004-05-08) |
Re: Basic-Like PCODE Compiler and Virtual Host/Interpreter Postmaster@paul.washington.dc.us (Paul Robinson) (2004-05-24) |
Re: Basic-Like PCODE Compiler and Virtual Host/Interpreter kenrose@tfb.com (Ken Rose) (2004-05-30) |
From: | Ken Rose <kenrose@tfb.com> |
Newsgroups: | comp.compilers |
Date: | 30 May 2004 13:19:55 -0400 |
Organization: | Posted via Supernews, http://www.supernews.com |
References: | 04-04-041 04-04-057 04-05-071 |
Keywords: | practice |
Posted-Date: | 30 May 2004 13:19:54 EDT |
Paul Robinson wrote:
> To me it makes sense to implement the
> compiler for a language in itself, if the language supports file I/O.
With all due respect, that's nuts. I understand the appeal of it, but
it presumes your language is good at the things compilers need, and
that's a lot more than file I/O. Garbage collection is worth it weight
in gold. Pattern matching syntax, for walking data structures like
trees, is better still.
- ken
Return to the
comp.compilers page.
Search the
comp.compilers archives again.