From: Joe Wreschnig <piman@...>
Date: 2002-07-08T10:41:48+09:00
Subject: Re: What to use for OS-specific module namespaces?


--=-tjLnMZF3+Mqn+U9v4K2k
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2002-07-07 at 20:01, Joe Wreschnig wrote:
> Hi all,
>=20
> I'm working on a Ruby module to parse/write to files in the Linux /proc
> filesystem (ACPI interfaces), and I was wondering if there's a preferred
> naming convention or namespace for things that are OS-specific. The base
> module is going to be called ACPI, with objects like ACPI::Processor and
> ACPI::Battery. Should I prepend something like System:: to ACPI? Or
> should I use something like Linux:: to be more specific? Or am I way
> off, and this stuff could go under the Kernel:: space (it seems to me
> that it doesn't fit with the rest of the code there)?

I don't usually talk to myself, but I just realized (stupidly) that the
notion of a Processor is more linked to the system than ACPI
specifically, and so this module will probably eventually grow into a
generic /proc reader (even if I don't intend it to right now). How does
Linux::Proc (with Linux::Proc::ACPI for the aforementioned bits) sound
with that in mind?
--=20
 - Joe Wreschnig <piman@sacredchao.net>  -  http://www.sacredchao.net
  "What I did was justified because I had a policy of my own... It's
   okay to be different, to not conform to society."
                                   -- Chen Kenichi, Iron Chef Chinese

--=-tjLnMZF3+Mqn+U9v4K2k
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA9KO3WTFkUq7Drx3cRArBqAJ957PASeamDFz1n1nDXw9D77Ifv6wCgqGdO
GvDDD2xJ+2iqk+LJbn5EDE4=
=PR3/
-----END PGP SIGNATURE-----

--=-tjLnMZF3+Mqn+U9v4K2k--