Re: Writing a compiler

Nick <Ibeam2000@gmail.com>
Sun, 26 Oct 2008 04:57:35 -0700 (PDT)

          From comp.compilers
Related articles
Writing a compiler andresjriofrio@gmail.com (andresj) (2008-10-20)
Re: Writing a compiler DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-10-23)
Re: Writing a compiler ademakov@gmail.com (Aleksey Demakov) (2008-10-23)
Re: Writing a compiler torbenm@pc-003.diku.dk (2008-10-23)
Re: Writing a compiler Juergen.Kahrs@vr-web.de (=?ISO-8859-1?Q?J=FCrgen_Kahrs?=) (2008-10-23)
Re: Writing a compiler m.collado@lml.ls.fi.upm.es (Manuel Collado) (2008-10-24)
Re: Writing a compiler Ibeam2000@gmail.com (Nick) (2008-10-26)
Re: Writing a compiler rajaram.officemails@gmail.com (RR) (2008-10-26)
Re: Writing a compiler andresjriofrio@gmail.com (andresj) (2008-10-29)
Re: Writing a compiler kamalpr@hp.com (kamal) (2008-10-29)
Re: Writing a compiler tony@my.net (Tony) (2008-10-31)
Re: Writing a compiler lkrupp@pssw.nospam.com.invalid (Louis Krupp) (2008-11-01)
Re: Writing a compiler marcov@stack.nl (Marco van de Voort) (2008-11-02)
[13 later articles]
| List of all articles for this month |
From: Nick <Ibeam2000@gmail.com>
Newsgroups: comp.compilers
Date: Sun, 26 Oct 2008 04:57:35 -0700 (PDT)
Organization: Compilers Central
References: 08-10-037 08-10-046
Keywords: code, design
Posted-Date: 26 Oct 2008 08:15:57 EDT

> Just use XSLT to generate the assembler code.


If I can make a suggestion, use C or C++ as target language. Here
you don't have to reinvent subroutine calling and the like, and you
maintain compatibility with other things on the OS. Not to mention
ease of moving around different OSes. And troubleshooting. Much
easier.
[Quite a reasonable idea unless your plan was to learn about code
generation. -John]


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.