Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!news.lightlink.com!news.iecc.com!nerds-end From: George Neuner Newsgroups: comp.compilers Subject: Re: Need an interesting topic for an undergraduate project on Compilers Date: Sat, 03 Sep 2011 16:00:18 -0400 Organization: A noiseless patient Spider Lines: 20 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <11-09-006@comp.compilers> References: <11-08-006@comp.compilers> <11-08-007@comp.compilers> <11-08-029@comp.compilers> <11-08-030@comp.compilers> <11-09-003@comp.compilers> <11-09-004@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: gal.iecc.com 1315089392 77610 64.57.183.58 (3 Sep 2011 22:36:32 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Sat, 3 Sep 2011 22:36:32 +0000 (UTC) Keywords: courses, C, code Posted-Date: 03 Sep 2011 18:36:32 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: x330-a1.tempe.blueboxinc.net comp.compilers:256 On Sat, 3 Sep 2011 06:43:30 +0100, Philip Herron wrote: >As for the backend outputting to C thread here, i dont recommend this >as i personally believe it will push you to produce bad IL and >middle-end code because you will rely too much on C. As a back end for a compiler I would agree with this. However, by coincidence, in another forum I am involved in a discussion regarding embedding a parser generator into a device so that its comm interface can be reconfigured or extended in the field by the end user. (There actually is a good reason for wanting to provide this 8-) Because most parser tools generate C source, the issue of embedding a C compiler also came up. >--Phil George