9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchovski@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] silly dhcpd question
Date: Sat, 14 May 2005 02:38:57 -0600	[thread overview]
Message-ID: <14ec7b1805051401384dc36d2@mail.gmail.com> (raw)
In-Reply-To: <72cca6a6583b9c78a245f4825fa65229@proxima.alt.za>

> (I haven't heard from Doug Gwyn for a long
> time)

doug relied on the usenet->9fans part of the gateway to work. he
hasn't posted since that stopped working.

i know this because i spotted his mails in comp.os.plan9 and notified
him that they don't make it to the list. i asked in 9fans who the
owner of the gateway is in order to get at least a couple of people's
emails to make it back here, but i got no reply.

doug does post, his last one in comp.os.plan9 is from the 4th of may.
i'll take the liberty of quoting it here:

----
p...@post.cz wrote:
> i suppose it is a bad manner to #include foo1.h from within foo.h
> is it?

Not as such.  If foo1.h defines the interface to some
resources that foo.h needs, then it *ought* to be
#included, so that the user of foo.h doesn't need to
know implementation details.  For example, if foo.h
declares a structure maintained by functions in the
"foo" package (also declared by foo.h) and that
structure has a private member that is a Boolean
flag, foo.h ought to be #including <stdbool.h> so
that it can use the proper type for "bool".  This
is generic advice, and the Plan9 developers seem to
disagree (for no good reason so far as I have heard).
----

to see all other posts authored by him:

http://groups-beta.google.com/groups?q=group:comp.os.plan9+author:gwyn&start=0&scoring=d&num=10&hl=en&lr=&as_drrb=q&as_mind=1&as_minm=1&as_miny=1981&as_maxd=14&as_maxm=5&as_maxy=2005&safe=off&

andrey

ps: sorry about the third person, douglas.


  reply	other threads:[~2005-05-14  8:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13 21:59 Ronald G. Minnich
2005-05-13 22:04 ` "Nils O. Selåsdal"
2005-05-13 22:28   ` Ronald G. Minnich
2005-05-14  2:36     ` boyd, rounin
2005-05-14  5:44 ` lucio
2005-05-14  8:05   ` lucio
2005-05-14  8:38     ` andrey mirtchovski [this message]
2005-05-14  8:40       ` andrey mirtchovski
2005-05-14 16:18         ` Russ Cox
2005-05-14 16:31           ` boyd, rounin
2005-05-14 18:59             ` Axel Belinfante
2005-05-14 19:11               ` Russ Cox
2005-05-16  4:04               ` Ronald G. Minnich

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=14ec7b1805051401384dc36d2@mail.gmail.com \
    --to=mirtchovski@gmail.com \
    --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).