[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: dylan availability
- To: email@example.com (Ted "Theodore" W. Leung)
- Subject: Re: dylan availability
- From: Bob Kerns <firstname.lastname@example.org>
- Date: Tue, 29 Sep 92 16:49:00 -0400
- Cc: email@example.com, firstname.lastname@example.org (Kevin Altis), email@example.com, firstname.lastname@example.org
- In-reply-to: Your message of "Tue, 29 Sep 92 15:15:54 EDT." <9209291915.AA20947@boojum.cs.brown.edu>
Date: Tue, 29 Sep 92 15:15:54 -0400
From: email@example.com (Ted "Theodore" W. Leung)
Bob Kerns writes:
> But this old compiler writer thinks Dylan would be a bit easier to
> write compilers for than a lot of them.
What did you have in mind when you said this? The only thing that I
can think of that's a little easier is that there's trivial syntax
analysis. The runtime system need to be fairly complicated (if you're
not embedding in lisp), and all the generic function and multiple
inheritance stuff should add complexity to a compiler. Just look what
happened between C and C++....
To avoid getting into a long discussion, let me just point out that you
have to read what I said. Languages like ADA and Common Lisp impose lots
of burdens on the compiler writer which are absent in Dylan because of
its simplicity. The point isn't that it's a whole lot easier, but rather
that they're all hard, but Dylan isn't especially hard.
The object system isn't that hard. (I've written object systems. Object
systems are a friend of mine. C++ is no object system ;=). Compared to
the overall size of a commercial-grade compiler, it's not going to be the
One of the best advantages is that you're going to get to write the compiler
in Dylan instead of C++. Lisp has proven to be a very good language for
writing compilers in.