9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] cfront c++
Date: Tue,  6 Nov 2007 17:27:26 -0500	[thread overview]
Message-ID: <8B2E4A25-29E7-4AE5-879B-FDB5AA3D14B9@mac.com> (raw)
In-Reply-To: <62776a2cf161fdcb87ebab04890d96b9@quintile.net>

cool :-) will it be a separate program or part of *c?

On Nov 6, 2007, at 2:58 PM, Steve Simon wrote:

> The first and seccond editions of plan9 included the cfront
> c++ preprocessor binaries, the third and fourth editions did not.
>
> AT&T have released the source of the cfront compiler and the labs
> have released the source of their port (read plan9-ised).
>
> I have updated the plan9 version (v3.01) to the last available from
> the AT&T (3.03). I did this more as a learning experience rather
> than to use the compiler in anger.
>
> Cfront is very old in c++ terms and is not very useful for compiling
> modern code. The only c++ code in the plan9 distribution is the
> postprocessor for the pm troff macro package.
>
> My port is mostly complete - it self hosts and compiles the pm  
> postprocessor
> however it is not finished. The task library is not ported, and  
> there is no
> Standard Component library (though this is avalable), Standard  
> Template
> library (much more work) and incomplete vlong support (I ran out of  
> patience).
>
> I am unlikely to get any further with this, anyone who is  
> interested can
> pick up what I have done, some notes, ideas, and links to the AT&T  
> and labs
> distributions here:
>
> 	http://www.quintile.net/plan9/c++
>
> -Steve


  reply	other threads:[~2007-11-06 22:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06 19:58 Steve Simon
2007-11-06 22:27 ` Pietro Gagliardi [this message]
2007-11-06 22:32   ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8B2E4A25-29E7-4AE5-879B-FDB5AA3D14B9@mac.com \
    --to=pietro10@mac.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).