From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: RE: [9fans] gcc trouble
Date: Fri, 21 Nov 2003 08:46:57 +0000 [thread overview]
Message-ID: <c06f3a9e4d4bfed631941e229719d76d@caldo.demon.co.uk> (raw)
In-Reply-To: <ACCF003CBA3D09458207DB0CB86AD17D124C39@XMAIL.asuch.cas.cz>
[-- Attachment #1: Type: text/plain, Size: 69 bytes --]
how many of those do you think could be handled by a recent cfront?
[-- Attachment #2: Type: message/rfc822, Size: 2526 bytes --]
From: <cej@gli.cas.cz>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] gcc trouble
Date: Fri, 21 Nov 2003 08:08:51 +0100
Message-ID: <ACCF003CBA3D09458207DB0CB86AD17D124C39@XMAIL.asuch.cas.cz>
> I believe that plan9 needs a C++ compiler (I know that you disagree).
Yes, I disagree. However, I would *love* to have (working) C++ for porting existing progs I need :-(
before I hire a programmer to rewrite them to (Plan9's) C.
++pac.
---
Odchozí zpráva neobsahuje viry.
Zkontrolováno antivirovým systémem AVG (http://www.grisoft.cz).
Verze: 6.0.541 / Virová báze: 335 - datum vydání: 14. 11. 2003
next prev parent reply other threads:[~2003-11-21 8:46 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 7:08 cej
2003-11-21 8:46 ` Charles Forsyth [this message]
2003-11-21 9:53 ` Skip Tavakkolian
-- strict thread matches above, loose matches on Subject: below --
2003-11-11 7:05 cej
2003-11-11 7:01 cej
2003-11-07 16:27 cej
2003-11-07 17:58 ` mirtchov
2003-11-07 16:53 ` Russ Cox
2003-11-07 19:14 ` mirtchov
2003-11-07 19:36 ` Russ Cox
2003-11-07 19:48 ` mirtchov
2003-11-07 19:56 ` Christopher Nielsen
2003-11-07 20:47 ` ron minnich
2003-11-07 21:05 ` Christopher Nielsen
2003-11-07 21:11 ` Charles Forsyth
2003-11-07 22:34 ` mirtchov
2003-11-08 0:08 ` Latchesar Ionkov
2003-11-08 1:35 ` Russ Cox
2003-11-08 1:54 ` Latchesar Ionkov
2003-11-08 2:14 ` Russ Cox
2003-11-08 4:35 ` ron minnich
2003-11-08 4:57 ` Geoff Collyer
2003-11-08 5:05 ` ron minnich
2003-11-08 8:24 ` Charles Forsyth
2003-11-08 17:29 ` ron minnich
2003-11-10 10:01 ` Douglas A. Gwyn
2003-11-11 0:16 ` Latchesar Ionkov
2003-11-12 23:46 ` Charles Forsyth
2003-11-20 14:33 ` Latchesar Ionkov
2003-11-20 18:34 ` boyd, rounin
2003-11-20 21:14 ` Latchesar Ionkov
2003-11-20 21:27 ` boyd, rounin
2003-11-20 21:35 ` mirtchov
2003-11-20 22:45 ` Latchesar Ionkov
2003-11-21 10:02 ` Fco.J.Ballesteros
2003-11-20 19:27 ` Joel Salomon
2003-11-20 20:03 ` Peter Bosch
2003-11-20 20:49 ` Christopher Nielsen
2003-11-20 21:01 ` boyd, rounin
2003-11-20 23:11 ` Joel Salomon
2003-11-20 23:28 ` boyd, rounin
2003-11-21 0:19 ` Christopher Nielsen
2003-11-21 0:31 ` boyd, rounin
2003-11-10 15:53 ` Joel Salomon
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=c06f3a9e4d4bfed631941e229719d76d@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).