From: rmoser <mlmoser@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Coding regulations
Date: Fri, 25 Apr 2003 22:14:12 -0400 [thread overview]
Message-ID: <200304252214120970.019AF211@smtp.comcast.net> (raw)
Yeah just a quick question. Not that I am actually able to code kernel
level drivers (I wish), but when I do code that would be part of one, I would
prefer not to make it a hassle for others to impliment.
To the point, I tend to do C++ classes, then make a C interface. Makes
it easier for me to program. Now, you may not want to mess with the C++
and convert it over, plus you may not want C++ code in the kernel. I am
about to start on the compression code for the fast algorithm that may be
used for kernel swap compression and compressed swap-on-ram, assuming
these swap modules are implimented. I don't want to cause any... oddities.
The C interfaces are just C functions that take a numerical handle which
identifies a class in a self-sorting linked list, as well as all the other data that
goes to each member function of the classes. I can still do it in C alone but
it's a little more work. Just don't wanna mess anyone/anything up.
--Bluefox Icy
next reply other threads:[~2003-04-26 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 2:14 rmoser [this message]
2003-04-26 9:21 ` Jörn Engel
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=200304252214120970.019AF211@smtp.comcast.net \
--to=mlmoser@comcast.net \
--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
all inboxes | Powered by JetHome®