From: Tim Bird <tim.bird@am.sony.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Martin Hunt <hunt@redhat.com>, systemtap@sources.redhat.com
Subject: Re: how to handle userspace string copy failures
Date: Thu, 25 May 2006 22:42:00 -0000 [thread overview]
Message-ID: <447632B0.3090203@am.sony.com> (raw)
In-Reply-To: <20060525212020.GK19134@redhat.com>
Frank Ch. Eigler wrote:
>>>> At worst, I think we should print warnings. I also propose that any
>>>> user_string() request that fails should return "<unknown>".
>>> I am uncomfortable with hard-coding such a decorated english term. A
>>> simple blank string would be fine.
>> blank strings do nothing to indicate that information was missing.
>
> Nor does "<unknown>", except to an english-speaking user looking over
> a literally transcribed output after the fact. That's the point.
The string "<unknown>" has much more information content,
even for a non-english speaker, than "". At least you
can google it.
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================
prev parent reply other threads:[~2006-05-25 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 18:11 Martin Hunt
2006-05-25 19:22 ` Frank Ch. Eigler
2006-05-25 21:05 ` Martin Hunt
2006-05-25 21:20 ` Frank Ch. Eigler
2006-05-25 22:42 ` Tim Bird [this message]
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=447632B0.3090203@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=fche@redhat.com \
--cc=hunt@redhat.com \
--cc=systemtap@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).