|C++ as implementation language in compiler design crse firstname.lastname@example.org (1994-12-12)|
|C++ as implementation language in compiler design crse email@example.com (1994-12-14)|
|Re: C++ as implementation language in compiler design crse firstname.lastname@example.org (1994-12-15)|
|Re: C++ as implementation language in compiler design crse email@example.com (1994-12-17)|
|Re: C++ as implementation language in compiler design crse firstname.lastname@example.org (1994-12-17)|
|From:||email@example.com (Steve Simmons)|
|Organization:||CONVEX News Network, Engineering (cnn.eng), Richardson, Tx USA|
|Date:||Wed, 14 Dec 1994 13:40:15 GMT|
> Do you anticipate that you will be using C++ as the implementation
> language of choice in your compiler design course, in the 1996-1997
> academic year? If not, why not?
IMHO, you should not force an implementation language on the students,
especially a new one and especially C++.
- There is enough real work in a compiler course that hoisting a new
language on them is ridiculous.
- Compiler internals do not blend well with O-O structure.
- YACC and LEX work real well with C but not so well with C++.
When I taught a compiler course, I used C as the default language for
examples, but they were allowed to code in whatever lanaguage that
they wanted. I believe that students should work in what they feel
comfortable on in such a complex matter. Let an O-O class introduce
them to C++. Take a class to discuss implementation issues associated
with inheritance, overloading, and virtual functions.
Return to the
Search the comp.compilers archives again.