--jX1bM1D+Mt/z9sU5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 04, 2007 at 05:54:02PM +0900, YAMAMOTO Takashi wrote:
> > On Mon,  3 Sep 2007 12:05:11 +0900 (JST)
> > yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi) wrote:
> >=20
> > > "generic string" means a opaque value whose meaning is only known to
> > > the specific driver, right?  does the opaqueness help the script?
> >=20
> > My intention wasn't to make it opaque, ENVSYS_GSTRING uses the
> > genstr member in envsys_data_t that is defined as:
> >=20
> > char genstr[ENVSYS_DESCLEN]
> >=20
> > so it's an array of 32 chars. But it's generic in the sense that you
> > can add the string that you want on it, perhaps the name is not the
> > best one... but I was out of ideas.
>=20
> i'm not sure how it's generic, compared to, say, ENVSYS_INTEGER.
> are you going to rename ENVSYS_INTEGER to ENVSYS_GINTEGER? :-)

GINTEGER is definitely less appealing than a GSTRING.  Granted, the
latter covers little, to the point one could doubt its usefulness,
but if it's a way to show something to the user while hiding the
internals of the...  hum, device, then it's good.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"You could have made it, spitting out benchmarks
Owe it to yourself not to fail"
Amplifico, Spitting Out Benchmarks, Hometakes Vol. 2, 2005.

--jX1bM1D+Mt/z9sU5
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (NetBSD)

iQEVAwUBRt0uQtgoQloHrPnoAQI6UQgAleVzuylgowWkfxOq6FJO8o9RQzqI6n5K
7OkZyxIjcJx2dPYYcu+HvF5mD5mqbvokEvT7QEBebvsxLr4Se7xdEseeCp0jUG2c
tCmm3kDiGR2RaT0utN2n3+SxF0G75mYdtRBCUtBjA8hGWEb5z2yYfLWTl3MpRzzS
SRHgdyPBcmtVDK6mWSU5Q9mC5a2kIiiDdAKTLKZWCXz5kB5KG5z+DLpetR311bkE
HktR3WAfF+6jxd8/kCdXeRvlaVUgA4CtUH97qSYC7VZaljuniGRyJZYjMVQj/cEt
TDF89uxXC499FcSm7SPZrIclntS6VD86G70LchkG7C/ncxIef/IrRw==
=WT1x
-----END PGP SIGNATURE-----

--jX1bM1D+Mt/z9sU5--