Related articles |
---|
xml as intermediate representation khurana.tanuj@gmail.com (tanuj) (2005-09-17) |
Re: xml as intermediate representation Juergen.Kahrs@vr-web.de (=?ISO-8859-1?Q?J=FCrgen_Kahrs?=) (2005-09-17) |
Re: xml as intermediate representation jeffrey.kenton@comcast.net (Jeff Kenton) (2005-09-22) |
Re: xml as intermediate representation touati@prism.uvsq.fr (TOUATI Sid) (2005-09-22) |
Re: xml as intermediate representation kers@hpl.hp.com (Chris Dollin) (2005-09-23) |
Re: xml as intermediate representation vidar.hokstad@gmail.com (Vidar Hokstad) (2005-09-23) |
Re: xml as intermediate representation demakov@ispras.ru (Alexey Demakov) (2005-09-27) |
Re: xml as intermediate representation vidar.hokstad@gmail.com (Vidar Hokstad) (2005-09-27) |
Re: xml as intermediate representation touati@prism.uvsq.fr (TOUATI Sid) (2005-09-30) |
From: | Chris Dollin <kers@hpl.hp.com> |
Newsgroups: | comp.compilers |
Date: | 23 Sep 2005 15:51:36 -0400 |
Organization: | HPLB |
References: | 05-09-078 05-09-110 |
Keywords: | analysis, optimize |
Posted-Date: | 23 Sep 2005 15:51:36 EDT |
TOUATI Sid wrote:
> I was an internal witness of a research project that used XML as an
> intermediate form for a compiler. XML is appropriate for such feature
> (it can be used to pass complex information between complex
> compilation steps).
Certainly it can. But what /advantage/ does it offer over something
significantly simpler (and more compact) to read and write?
[Not to mention that having the steps share memory - eg by being in
the same application - makes it even easier to pass information
around, without (de)serialisation overheads.]
--
Chris "electric hedgehog" Dollin
The software engineer's song: "who knows where the time goes".
Return to the
comp.compilers page.
Search the
comp.compilers archives again.