From: "Eduardo Pérez" <100018135@alumnos.uc3m.es>
To: linux-kernel@vger.kernel.org
Subject: [RFC] namespace clean
Date: Mon, 7 Oct 2002 10:17:50 +0000 [thread overview]
Message-ID: <a6cf5427338512cb0ae6b015e16b896a@alumnos.uc3m.es> (raw)
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 ?
next reply other threads:[~2002-10-07 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 10:17 Eduardo Pérez [this message]
2002-10-07 15:16 ` [RFC] namespace clean george anzinger
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=a6cf5427338512cb0ae6b015e16b896a@alumnos.uc3m.es \
--to=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;
as well as URLs for NNTP newsgroup(s).