From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_20Mp82XuUeQbBmJkEBA0rA)" Date: Wed, 25 Mar 2009 18:11:26 -0700 From: "Roman V. Shaposhnik" In-reply-to: <9bab1584ddc2c1730933f3047c024018@terzarima.net> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-id: <49CAD63E.9020902@Sun.COM> References: <9bab1584ddc2c1730933f3047c024018@terzarima.net> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Subject: Re: [9fans] request for more GSoC project suggestions Topicbox-Message-UUID: c60c247c-ead4-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --Boundary_(ID_20Mp82XuUeQbBmJkEBA0rA) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT On 03/25/09 02:12 PM, Charles Forsyth wrote: >> A modern cfront is nearly impossible. Templates make it hella-hard. >> > > really? how is that? > Everything is possible. It is software, after all. But it is not practical. The original cfront was, to some extent, a cpp(1) on steroids. AFAIR, it operated by manipulating C source code. With modern C++ things like inlines, templates and concepts operate at a level of AST. I guess one could use C for an AST representation, but that would be a pretty daring feat. Thanks, Roman. --Boundary_(ID_20Mp82XuUeQbBmJkEBA0rA) Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT On 03/25/09 02:12 PM, Charles Forsyth wrote:

A modern cfront is nearly impossible.  Templates make it hella-hard.


really? how is that?

Everything is possible. It is software, after all. But it is not practical. The
original cfront was, to some extent, a cpp(1) on steroids. AFAIR, it operated
by manipulating C source code.

With modern C++ things like inlines, templates and concepts operate at
a level of AST. I guess one could use C for an AST representation, but
that would be a pretty daring feat.

Thanks,
Roman.

--Boundary_(ID_20Mp82XuUeQbBmJkEBA0rA)--