From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Interested in improving networking in Plan 9
Date: Mon, 31 Aug 2009 13:32:30 -0400 [thread overview]
Message-ID: <9ab217670908311032x5401e505yb78cb76b79355368@mail.gmail.com> (raw)
In-Reply-To: <fcacaaedb15d35332c8f5d76a5c2fd02@coraid.com>
2009/8/31 erik quanstrom <quanstro@coraid.com>:
>> 2009/8/31 Bakul Shah <bakul+plan9@bitblocks.com>:
>> > But this is nasty!
>> > % cat ndb/dom/'' # same as ndbquery dom ''
>>
>> No, the nasty part is really that the file should be called `.' and
>> the filesystem reserves dot as the reference to the current directory.
>> You could probably call the file `dot' or `root' (cat ndb/dom/dot or
>> cat ndb/dom/root) as something that shouldn't ever conflict with
>> anything else -- but the root of DNS is not an empty string.
>
> aren't you being a little bit pedantic? quoting is a fact
> of life. we don't say that it's evil to need to quote or
> transform things in rc or smtp to deal with local requirements.
> why would it be evil to quote '.'? and why would be calling
> '.' 'root' or 'dot' rather than '' be any less evil?
It's (in my opinion) slightly less evil because if(!strlen(name))
seems like a pretty poor way to determine that you're looking at the
root zone. It's also more intuitive and easier to document that you're
looking at the root than saying `to find root, look for a file named
as an empty string'. So: less evil because it makes code more
intuitive and it makes documentation easier.
Also, I think I should state that I really don't care about
implementation as long as it's documented, and that the root is not an
empty string. I don't particularly care about quoting at all, and I
don't consider that any reason for one method to be more obtuse than
another.
--dho
> - erik
>
>
next prev parent reply other threads:[~2009-08-31 17:32 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 7:21 Vinu Rajashekhar
2009-08-30 14:21 ` ron minnich
2009-08-30 16:19 ` Eric Van Hensbergen
2009-08-30 17:07 ` erik quanstrom
2009-08-30 17:40 ` Venkatesh Srinivas
2009-08-30 17:53 ` erik quanstrom
[not found] ` <c81a07350908300842w3df8321aidf55096b65eb9b77@mail.gmail.com>
2009-08-30 18:17 ` ron minnich
2009-08-30 18:35 ` ron minnich
2009-08-31 3:34 ` erik quanstrom
2009-08-31 12:45 ` Eric Van Hensbergen
2009-08-31 12:51 ` erik quanstrom
2009-08-31 12:59 ` Vinu Rajashekhar
2009-08-31 13:05 ` erik quanstrom
2009-08-31 13:48 ` Anthony Sorace
2009-08-31 14:51 ` Devon H. O'Dell
2009-08-31 15:03 ` Vinu Rajashekhar
2009-08-31 13:42 ` Eric Van Hensbergen
2009-08-31 14:04 ` erik quanstrom
2009-08-31 14:25 ` Eric Van Hensbergen
2009-08-31 14:36 ` erik quanstrom
2009-08-31 14:57 ` Eric Van Hensbergen
2009-08-31 15:52 ` erik quanstrom
2009-08-31 16:12 ` Eric Van Hensbergen
2009-08-31 14:55 ` Francisco J Ballesteros
2009-08-31 15:09 ` Eric Van Hensbergen
2009-08-31 15:56 ` erik quanstrom
2009-08-31 16:16 ` Bakul Shah
2009-08-31 16:33 ` Eric Van Hensbergen
2009-09-02 16:50 ` Bakul Shah
2009-09-02 17:10 ` Robert Raschke
2009-09-03 11:21 ` matt
2009-09-03 12:50 ` erik quanstrom
2009-09-03 16:13 ` Anthony Sorace
2009-09-03 16:29 ` erik quanstrom
2009-09-03 16:34 ` Robert Raschke
2009-09-03 21:50 ` Daniel Lyons
2009-09-03 19:08 ` Steve Simon
2009-08-31 17:09 ` Devon H. O'Dell
2009-08-31 17:20 ` erik quanstrom
2009-08-31 17:32 ` Devon H. O'Dell [this message]
2009-08-31 18:00 ` erik quanstrom
2009-08-31 4:17 ` Federico G. Benavento
2009-08-31 4:53 ` Vinu Rajashekhar
2009-08-30 17:22 erik quanstrom
2009-08-30 17:36 ` Vinu Rajashekhar
2009-08-30 17:56 ` 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=9ab217670908311032x5401e505yb78cb76b79355368@mail.gmail.com \
--to=devon.odell@gmail.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).