From: "Rob Pike" <robpike@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] shared libraries
Date: Wed, 19 Apr 2006 07:21:49 +1000 [thread overview]
Message-ID: <7359f0490604181421j885ac13mec018f58857806db@mail.gmail.com> (raw)
In-Reply-To: <4445500C.90708@lanl.gov>
shared libraries are obviously a good idea until you've actually used them.
then whether it's obvious or not that they're a bad idea is mostly a matter
of how close you are to trying to get them to work.
-rob
next prev parent reply other threads:[~2006-04-18 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 17:54 Russ Cox
2006-04-18 17:03 ` Charles Forsyth
2006-04-18 18:14 ` Russ Cox
2006-04-18 17:17 ` Charles Forsyth
2006-04-18 17:25 ` Bruce Ellis
2006-04-18 17:39 ` uriel
2006-04-18 18:03 ` uriel
2006-04-18 18:57 ` Charles Forsyth
2006-04-18 19:20 ` Russ Cox
2006-04-18 20:46 ` Ronald G Minnich
2006-04-18 21:21 ` Rob Pike [this message]
2006-04-18 21:26 ` Brantley Coile
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=7359f0490604181421j885ac13mec018f58857806db@mail.gmail.com \
--to=robpike@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).