Related articles |
---|
Teaching compilers backwards? andy@galois.com (Andy Gill) (2003-09-23) |
Re: Teaching compilers backwards? Trevor.Jenkins@suneidesis.com (2003-09-27) |
Re: Teaching compilers backwards? rbates@southwind.net (Rodney M. Bates) (2003-10-04) |
Re: Teaching compilers backwards? hat@se-126.se.wtb.tue.nl (Albert Hofkamp) (2003-10-08) |
Re: Teaching compilers backwards? rmatthewk@hotmail.com (2003-10-08) |
Re: Teaching compilers backwards? joachim.durchholz@web.de (Joachim Durchholz) (2003-10-12) |
Re: Teaching compilers backwards? peter_flass@yahoo.com (Peter Flass) (2003-10-13) |
Re: Teaching compilers backwards? Brian.Inglis@SystematicSw.ab.ca (Brian Inglis) (2003-10-13) |
Re: Teaching compilers backwards? michael.l.ross@intel.com (Michael Ross) (2004-03-11) |
Re: Teaching compilers backwards? rand@rice.edu (Randy Crawford) (2004-03-15) |
Re: Teaching compilers backwards? zork_666@nospammail.net (Johnathan) (2004-03-15) |
Re: Teaching compilers backwards? romesamo@earthlink.net (Rome Samo) (2004-03-19) |
Re: Teaching compilers backwards? aycock@cse.cpsc.ucalgary.ca (John Aycock) (2004-03-19) |
Re: Teaching compilers backwards? lex@cc.gatech.edu (Lex Spoon) (2004-03-19) |
[7 later articles] |
From: | Brian Inglis <Brian.Inglis@SystematicSw.ab.ca> |
Newsgroups: | comp.compilers |
Date: | 13 Oct 2003 00:25:57 -0400 |
Organization: | Systematic Software |
References: | 03-09-073 03-10-014 |
Keywords: | courses |
Posted-Date: | 13 Oct 2003 00:25:57 EDT |
On 4 Oct 2003 14:47:19 -0400 in comp.compilers, "Rodney M. Bates"
<rbates@southwind.net> wrote:
>Andy Gill wrote:
>
>> Has anyone ever taught compilers backwards? How did it work out?
>>
>> Traditionally, a compiler class starts with lexing, and flows downstream
>> towards register allocation and assembly language generation.
>>
>> I am considering starting a compiler class with assembly language exercises,
>> and having the students build a small compiler from the back, forward.
i.e. from the back to the front?
>Well, it seems like one obvious problem with this is that each
>phase uses as input, the output of the previous phase. And what
>that output is, both its format/syntax, and its deeper semantics, are
>things a compiler course student won't already know. And explaining
>that will considerably overlap just studying the previous phase.
It would seem to be a reasonable approach to teaching students what
the requirements of each previous phase are to allow the following
phase to do its work; perhaps allowing them to develop the
requirements themselves, increasing their understanding; rather than
being given the whole model front to back, trying to implement the
whole shebang, and having to rework everything from front to back if
relevant information is missed.
Thanks. Take care, Brian Inglis Calgary, Alberta, Canada
--
Brian.Inglis@CSi.com (Brian dot Inglis at SystematicSw dot ab dot ca)
fake address use address above to reply
Return to the
comp.compilers page.
Search the
comp.compilers archives again.