|Maintainable compiler design? firstname.lastname@example.org (=?ISO-8859-1?Q?Christoffer_Lern=F6?=) (2009-07-27)|
|Re: Maintainable compiler design? email@example.com (Michiel) (2009-07-29)|
|Re: Maintainable compiler design? firstname.lastname@example.org (BGB / cr88192) (2009-07-29)|
|Re: Maintainable compiler design? email@example.com (Martin Ward) (2009-08-06)|
|Re: Maintainable compiler design? firstname.lastname@example.org (James Harris) (2009-08-06)|
|From:||James Harris <email@example.com>|
|Date:||Thu, 6 Aug 2009 15:37:21 -0700 (PDT)|
|Posted-Date:||07 Aug 2009 09:45:42 EDT|
On 27 July, 22:16, Christoffer Lernv <le...@dragonascendant.com>
> I am working with my pet language, defining grammar, building runtime
> etc - the usual things.
> However, as this is my first complier, I am worried that I'm not
> organising the code well. Aside from the frontend/backend division, I
> feel the compiler books I red are sort of hazy in regards to how to
> solidly organize the compiler to ensure that it is easy to maintain. ...
There are some general programming principles: data hiding, modules,
narrow interfaces. Specifically for compilers the organisation of
Appel from his Modern Compiler Implementation books makes a lot of
sense. You don't have to use all the modules he lists. If you don't
have access to any of his books the set of modules is listed at
Look for message 71.
Return to the
Search the comp.compilers archives again.