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] MirOS ksh (mksh) building out-of-the box on Plan9/APE
Date: Sun, 28 Jul 2013 07:38:51 +0200	[thread overview]
Message-ID: <6100054cf81e1a26e75fd335d50d97e9@proxima.alt.za> (raw)
In-Reply-To: <d34d6ce6c7d5b8da53d3bf53fd8f739e@brasstown.quanstro.net>

> SIGCHLD is not defined for plan 9, except in ape.  that's what i
> would call ape-specific.

This is degenerating into politics (or religion, same thing) quite
unnecessarily.

In my opinion, Go is a "better" APE (I'm convinced that Rob agrees
with me :-).  The way I see it and the reason I like Go a lot, is that
it seems to aim to great portability across different platforms.  In
my particular dream I saw myself developing in the comfort of Plan 9
for the Windows environment (when that still mattered) and today for
the mobile phone and various tablets (somebody keeps moving the goal
posts, but we'll catch them eventually).

In this respect, Go is perhaps closer to Posix than to APE, and then
maybe not: these are intentionally closely coupled.  Where
SIGCLD/SIGCHLD (evidently Posix didn't quite get this one nailed down)
is concerned, APE and Go need to provide the same service and
therefore need to duplicate the implementation.  If, as cinap
suggests, there is no support in the kernel for it and it cannot be
implemented purely in user user space, then it makes sense to do the
job once, in the kernel and I'd like to leave it to those who are
familiar with such things to determine what is actually necessary.

But I think it is clear that Go and APE can retain their separation,
migrating Go to APE makes no sense at all.

++L




  parent reply	other threads:[~2013-07-28  5:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26  6:59 Jens Staal
2013-07-26 16:26 ` cinap_lenrek
2013-07-26 17:01   ` erik quanstrom
2013-07-27  5:48     ` Jens Staal
2013-07-27 14:01       ` erik quanstrom
2013-07-27 15:11         ` Aram Hăvărneanu
2013-07-27 15:23           ` erik quanstrom
2013-07-27 21:39             ` Kurt H Maier
2013-07-27 21:43               ` erik quanstrom
2013-07-27 22:39                 ` Aram Hăvărneanu
2013-07-28  0:55                   ` erik quanstrom
2013-07-28  5:38                 ` lucio [this message]
2013-08-16  7:26 ` Jens Staal

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=6100054cf81e1a26e75fd335d50d97e9@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).