From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] a question on style
Date: Fri, 1 Aug 2008 12:28:33 -0400 [thread overview]
Message-ID: <B3E31889-401C-47BD-887C-F14FDA602DDE@mac.com> (raw)
In-Reply-To: <a8a5a21f87547efa8127bcf5d5af847d@quintile.net>
On Aug 1, 2008, at 11:37 AM, Steve Simon wrote:
>> OK, am I just out of date or is there a real reason for linker
>> sets?
>
> I see it this way:
>
> using linker sets means you have to learn and understand the
> linkers language
> to understand how the system is configured (when trying to track
> down a problem)
>
> using a bit of script to generate some tables of C code you just
> need to
> know C.
>
> This combined with the theroy that there is too much to learn and
> the less new stuff
> I need to learn to get a job done the better makes the choice easy
> (IMHO).
>
> -Steve
>
Plus, linker sets are nonportable. I don't see 8l supporting them, so
I don't think we'll be using them... but all the world uses GCC
nowadays, so why bother with portability anymore?
next prev parent reply other threads:[~2008-08-01 16:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <af2f03a68f1be3c97a367093315a9f56@quanstro.net>
2008-07-31 22:19 ` ron minnich
2008-08-01 15:37 ` Steve Simon
2008-08-01 16:28 ` Pietro Gagliardi [this message]
2008-08-01 17:24 ` Charles Forsyth
2008-08-01 22:29 ` erik quanstrom
2008-08-03 11:27 ` bblochl
2008-08-05 22:38 ` erik quanstrom
2008-08-01 11:41 erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2008-07-31 22:17 erik quanstrom
2008-07-31 22:02 ron minnich
2008-07-31 22:04 ` erik quanstrom
2008-07-31 22:15 ` ron minnich
2008-08-01 9:26 ` Roman V. Shaposhnik
2008-08-01 10:06 ` erik quanstrom
2008-08-01 11:09 ` Roman V. Shaposhnik
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=B3E31889-401C-47BD-887C-F14FDA602DDE@mac.com \
--to=pietro10@mac.com \
--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).