--5xSkJheCpeK0RUEJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 19, 2006 at 12:49:31PM +0900, YAMAMOTO Takashi wrote:
> > On Tue, Sep 19, 2006 at 07:34:32AM +0900, YAMAMOTO Takashi wrote:
> >=20
> > I'm assuming that not everything in the dictionary needs a shadow=20
> > variable. If that's wrong (i.e. everything needs a shadow variable),=20
> > there's no point.
> >=20
> > I also expect that we will be adding more-general device driver uses fo=
r=20
> > a dictionary. So we will have both "non-shadow-variable" uses for a dic=
t,=20
> > and we will need to figure out how to handle this eventually.
>=20
> can you explain why you think an item should be in both of
> "shadow variables" and a dictionary?
> i don't see any benefit to use proplib dictionary here...

So we can have a dictionary that contains the "state" of the device. So=20
that all of the state moves around as one.

The whole idea is to use "shadow variables" as a way to let us effectively=
=20
use a dictionary for things we techically can't. Obviously we'd only do=20
this if it made sense...

Take care,

Bill

--5xSkJheCpeK0RUEJ
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFFD28XWz+3JHUci9cRAvXsAJ9Wf1g0cyeWUl1uNfeyNvQlybx0MQCfXKTc
AKlyQKFgJUe91fmVmHP609Q=
=cUVo
-----END PGP SIGNATURE-----

--5xSkJheCpeK0RUEJ--