9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] formatting the manual from plan9 ports?
Date: Wed, 30 May 2012 05:44:41 +0200	[thread overview]
Message-ID: <a7da0139aa96cc7db4ca3c14a688ed9c@rei2.9hal> (raw)
In-Reply-To: <201205292046.q4TKkoqZ010156@skeeve.com>

short hardcoded paths are an advantage. this is not linux. this
is plan9. there are rules. the kernel already provides a way for
indirection that works for *everything*. mount/bind and private
namespaces.

no need to reimplement indirection in every program over and
over again.

a hardcoded path expresses an intent. you can look at it and you
know what it expects because ususly the stuff it points to is
already there or has an established meaning. (read namespace(4))

this is better than enviroment variables like $FOOBARBAZPATH
because it hides the default somewhere in the program, or it will
just fail when not specified giving me no clue what $FOOBARBAZPATH
is supposed to be. theres also complexity involved in the
implementatoin. using a hardcoded paths is great. you just let
the program fail with sysfatal("%r"); and it will show the path
it tired to open in the error message giving immidiate clue what
it needs.

--
cinap



  parent reply	other threads:[~2012-05-30  3:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 19:03 Aharon Robbins
2012-05-25 19:08 ` pmarin
2012-05-29 20:46   ` Aharon Robbins
2012-05-29 21:05     ` erik quanstrom
2012-05-30  3:44     ` cinap_lenrek [this message]
2012-05-30  4:03       ` erik quanstrom
2012-05-30  6:11 arnold
2012-05-30 12:38 ` erik quanstrom

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=a7da0139aa96cc7db4ca3c14a688ed9c@rei2.9hal \
    --to=cinap_lenrek@gmx.de \
    --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).