All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Joerg Schilling <schilling@fokus.fraunhofer.de>
Cc: linux-kernel@vger.kernel.org, jengelh@linux01.gwdg.de,
	drepper@redhat.com, austin-group-l@opengroup.org
Subject: Re: The naming of at()s is a difficult matter
Date: Tue, 14 Feb 2006 09:35:50 -0800	[thread overview]
Message-ID: <43F214F6.1070206@zytor.com> (raw)
In-Reply-To: <43F20C95.nailMWZULDLNF@burner>

Joerg Schilling wrote:
>>
>>Surely you're not suggesting that TOG's job is to rubber-stamp bad 
>>Solaris decisions...
> 
> Are you interested in forcing Solaris to change all interfaces?
> 

In this case, I think it would be entirely appropriate.  It's hardly a 
hardship to maintain the legacy names for backwards compatibility; since 
those names are nonsensical it is unlikely they'll ever want to be 
claimed, in which case they can be maintained indefinitely.

However, I would find it much, much worse if names that are *actively 
misleading and confusing* to the programmer would be included in an 
international standard and therefore forced upon the rest of the world 
forever.

	-hpa

  reply	other threads:[~2006-02-14 17:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12  3:33 The naming of at()s is a difficult matter H. Peter Anvin
2006-02-12 10:37 ` Jan Engelhardt
2006-02-12 17:42   ` H. Peter Anvin
2006-02-13 14:09   ` Joerg Schilling
2006-02-13 15:56     ` H. Peter Anvin
2006-02-14  8:17     ` Jan Engelhardt
2006-02-14 15:09       ` Joerg Schilling
2006-02-14 15:21         ` H. Peter Anvin
2006-02-14 16:13           ` Matthew Frost
2006-02-14 17:00           ` Joerg Schilling
2006-02-14 17:35             ` H. Peter Anvin [this message]
2006-02-14 18:07         ` Jan Engelhardt
2006-02-14 18:12           ` H. Peter Anvin
2006-02-14 18:17             ` Jan Engelhardt
2006-02-14 18:53             ` Joerg Schilling
2006-02-14 18:51           ` Joerg Schilling
2006-02-12 14:41 ` Jim Meyering

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=43F214F6.1070206@zytor.com \
    --to=hpa@zytor.com \
    --cc=austin-group-l@opengroup.org \
    --cc=drepper@redhat.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schilling@fokus.fraunhofer.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.