From: Rick Hohensee <humbubba@smarty.smart.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] partial-Plan9ification question
Date: Fri, 13 Jul 2001 14:37:00 -0400 [thread overview]
Message-ID: <200107131837.OAA11168@smarty.smart.net> (raw)
In-Reply-To: <20010713180831.4A259199E7@mail.cse.psu.edu> from "brucee@plan9.bell-labs.com" at Jul 13, 2001 02:08:28 PM
>
> please consider no ifdefs ever. and assembly language
> only in vital library functions. sure we need
> /sys/src/libc/arm/memmove.s but there is
> /sys/src/libc/port/memmove.c
>
> your code may then be understandable and maintainable.
>
> #ifndef throw_up
> #define throw_up(p) chunder(p)
> #endif
>
> is really rather silly but prevalent.
>
> brucee
>
The existing unix I'm talking about (Linux 1.2.13) won't turn into Plan 9
style source overnight. I agree though. One thing I think I can get from
here is the only-include-me-once condoms, which I have some scripting done
for. That used to annoy the fire out of me in Amiga JForth. FORTH, fer
cryin out loud. (JForth was quite elegant mostly, BTW. "A
once-in-a-paradigm thing").
Rick Hohensee
www.clienux.com
next prev parent reply other threads:[~2001-07-13 18:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 18:08 brucee
2001-07-13 18:37 ` Rick Hohensee [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-13 22:34 David Gordon Hogan
2001-07-13 19:15 David Gordon Hogan
2001-07-13 6:39 David Gordon Hogan
2001-07-13 6:23 David Gordon Hogan
2001-07-13 18:26 ` Rick Hohensee
2001-07-13 5:53 forsyth
2001-07-13 6:26 ` Mike Haertel
2001-07-12 22:16 Rick Hohensee
2001-07-12 22:18 ` Boyd Roberts
2001-07-13 1:55 ` Rick Hohensee
2001-07-12 22:08 David Gordon Hogan
2001-07-13 1:27 ` Rick Hohensee
2001-07-13 14:53 ` Douglas A. Gwyn
2001-07-13 22:18 ` Dan Cross
2001-07-14 1:21 ` Boyd Roberts
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=200107131837.OAA11168@smarty.smart.net \
--to=humbubba@smarty.smart.net \
--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).