From: Kurt H Maier <khm-9@intma.in>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] APE inconsistencies
Date: Fri, 29 Mar 2013 15:12:20 -0400 [thread overview]
Message-ID: <20130329191220.GA9082@intma.in> (raw)
In-Reply-To: <20130329190345.GA2335@polynum.com>
On Fri, Mar 29, 2013 at 08:03:45PM +0100, tlaronde@polynum.com wrote:
> On Fri, Mar 29, 2013 at 01:26:53PM -0500, Jeff Sickel wrote:
> >
> > Though if I check recent FreeBSD manuals, it's all there. And given that
> > this is part of the BSD extensions to APE, those might be more relevant
> > than the Linux man pages. Not that BSD tries to be POSIX compliant
> > any more or less than GNU/Linux.
> >
>
> It should be indeed underlined that this is a compatibility feature, and
> not a POSIX feature. It seems that it is still here for legacy
> compatibility on BSD (it is still here in NetBSD for example) but the
> question arises whether it is worth supporting (because starting to
> support all not POSIX is a daunting task).
>
> This is what is said in the APE paper. The problem is not with Plan9
> APE, it is that there are not a lot of programs that are written in a
> POSIX compliant way...
>
It is a POSIX feature, I think. It's just an outmoded one. Supporting
all revisions of POSIX is damn near impossible. Does APE have an
explicit target?
khm
next prev parent reply other threads:[~2013-03-29 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 17:13 Jeff Sickel
2013-03-29 17:20 ` Charles Forsyth
2013-03-29 17:25 ` Jeff Sickel
2013-03-29 17:41 ` Kurt H Maier
2013-03-29 18:00 ` Charles Forsyth
2013-03-29 18:26 ` Jeff Sickel
2013-03-29 19:03 ` tlaronde
2013-03-29 19:12 ` Kurt H Maier [this message]
2013-03-29 20:10 ` tlaronde
2013-03-29 20:32 ` Charles Forsyth
2013-03-30 2:37 ` a
2013-03-29 22:20 ` Lyndon Nerenberg
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=20130329191220.GA9082@intma.in \
--to=khm-9@intma.in \
--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).