9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] APE printf difference
Date: Wed,  9 Jul 2008 13:12:40 +0200	[thread overview]
Message-ID: <87e08a731710ab0768f3af2faed0411a@proxima.alt.za> (raw)
In-Reply-To: <908ffff67002a2daaa46c0f1cb701a99@9srv.net>

> APE's export filter is very useful, and would be missed, but
> there's an equally valid import role that it isn't very good at
> serving, in modern contexts. I'd rather see that broken out
> into a distinct environment, say G(nu)APE.

Maybe a touch far-fetched, but could we not agree to use APE for
export and the GCC/G++ port for import?  Of course, mostly as a
principle and as focus, not as an obstacle.  If we accepted this as
the objective, more effort may go into making GCC/G++ viable.  I have
once again slipped back somewhat and I am not sure how easily I could
compute and submit the changes to the APE libraries and headers I
needed to apply to produce the GCC APE prerequisites.  It's on my TODO
list, but not a high priority.  Unfortunately, I need a clean
environment to reproduce the GCC port and that is pretty hard to
concoct for something that has few interested takers.

++L




      reply	other threads:[~2008-07-09 11:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-06 22:03 Fernan Bolando
2008-07-06 22:14 ` erik quanstrom
2008-07-06 23:04   ` Charles Forsyth
2008-07-07 21:01     ` Pietro Gagliardi
2008-07-07 21:21       ` erik quanstrom
2008-07-07 23:02       ` Charles Forsyth
2008-07-08  0:07         ` a
2008-07-09 11:12           ` lucio [this message]

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=87e08a731710ab0768f3af2faed0411a@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@9fans.net \
    /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).