The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: "Eduardo Pérez" <100018135@alumnos.uc3m.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] namespace clean
Date: Mon, 07 Oct 2002 08:16:02 -0700	[thread overview]
Message-ID: <3DA1A532.9BF70424@mvista.com> (raw)
In-Reply-To: a6cf5427338512cb0ae6b015e16b896a@alumnos.uc3m.es

Eduardo Pérez wrote:
> 
> Currently the Linux kernel has a cryptic api namespace that confuses
> many people when trying to code for the Linux kernel. People can't know
> by direct examination of a symbol to what package belongs. Also symbols
> can't be easily sorted by package.
> 
> I'm suggesting to use a cleaner namespace like
> package_object_method and package_function
> If this is accepted, symbols from new code should follow this
> naming, and current symbols should start the transition to this cleaner
> namespace.
> 
> If anybody like me think that this would help people to code for the
> Linux kernel it would be a good idea to start this transition to a
> cleaner namespace.
> 
> Most drivers and new core kernel api have a very clean namespace but
> some old api don't.
> 
> What are your thoughts about this ?

Then if it is a static symbol, one could use anything?  I.e.
static symbols would not follow the rule, right?
-- 
George Anzinger   george@mvista.com
High-res-timers: 
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml

  reply	other threads:[~2002-10-07 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07 10:17 [RFC] namespace clean Eduardo Pérez
2002-10-07 15:16 ` george anzinger [this message]
2002-10-07 16:14   ` Eduardo Pérez

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=3DA1A532.9BF70424@mvista.com \
    --to=george@mvista.com \
    --cc=100018135@alumnos.uc3m.es \
    --cc=linux-kernel@vger.kernel.org \
    /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