9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "peter a. cejchan" <pac@cejchan.gli.cas.cz>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Announce: port
Date: Mon, 29 Apr 2002 09:45:05 +0000	[thread overview]
Message-ID: <71652467.0204282150.4316235@posting.google.com> (raw)
In-Reply-To: <3CC93C53.2D0DEF98@strakt.com>

boyd@strakt.com (Boyd Roberts) wrote in message news:<3CC93C53.2D0DEF98@strakt.com>...
> "peter a. cejchan" wrote:
> > > Native is actually a lot easier.
> >
> > Really? I mean 'native' should be w UTF, w/o stdio.h, etc. Or does
> > native stdio.h treat char as wchar?
>
> stdio is horrible.  wchar's are a disaster.
>
> use bio:
>
>     http://plan9.bell-labs.com/magic/man2html/2/bio
>
> The compiler already understands about UTF and runes and so does
> libc (obviously):
>
>     http://plan9.bell-labs.com/sys/doc/comp.html
>
> Plan 9 is very close to unix, but it's not really.  A lot of grief
> gets caused by ape's heroic attempt to smash ANSI/POSIX into Plan 9.
>
> It only gets really nasty when you have to port something that uses
> the tty routines, sid's/pgrp's and signals -- most programs don't.

Oh, beat my English.  I was just curious if a native port, I mean
*without* APE and , hopefully, *without stdio.h* would be "a lot
easier" (when it means almost complete rewrite). Nevertheless,
although the program is very helpful for me, I must admit it is not
worth a rewrite: rather a complete redesign as an rc script using grep
and other standard utils.

++pac.


  parent reply	other threads:[~2002-04-29  9:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-25  7:33 Peter A. Cejchan
2002-04-25  9:04 ` Boyd Roberts
2002-04-26  8:47   ` peter a. cejchan
2002-04-26 11:38     ` Boyd Roberts
2002-04-29  9:40       ` Douglas A. Gwyn
2002-04-29  9:45       ` peter a. cejchan [this message]
2002-04-29 10:48         ` Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2002-04-25  7:55 forsyth
2002-04-25  7:22 forsyth
2002-04-26  8:47 ` peter a. cejchan

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=71652467.0204282150.4316235@posting.google.com \
    --to=pac@cejchan.gli.cas.cz \
    --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).