[oe-commits] Chris Larson : More sane naming for the variable typing code
git version control
git at git.openembedded.org
Wed Feb 9 19:12:03 UTC 2011
Module: openembedded.git
Branch: master
Commit: 2fbd56c0ef7df1b45746dbf9390805f2e67c590b
URL: http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=2fbd56c0ef7df1b45746dbf9390805f2e67c590b
Author: Chris Larson <chris_larson at mentor.com>
Date: Wed Feb 9 10:28:42 2011 -0700
More sane naming for the variable typing code
oe.types.value -> oe.data.typed_value
This name has been bugging me. This function is the primary interface to
the module for OE metadata, as it takes a variable name and datastore and
returns an object of the correct type. While this function is part of the
variable typing implementation, in reality it's more about giving you a
useful object from the metadata, so I think oe.data is a more appropriate
place for it.
oe.types -> oe.maketype
These are the functions which construct types, not the types themselves,
so it was somewhat misleading.
oe._types -> oe.types
These are the actual types, any callable in this module becomes an OE
type, using its arguments to determine the variable flags (optional and
required) to obey. Will use __init__'s args in the case of an actual
python class.
Signed-off-by: Chris Larson <chris_larson at mentor.com>
---
classes/base.bbclass | 14 +-
classes/typecheck.bbclass | 3 +-
lib/oe/_types.py | 104 -----------------
lib/oe/data.py | 13 ++
lib/oe/maketype.py | 97 ++++++++++++++++
lib/oe/test_types.py | 2 +-
lib/oe/types.py | 176 ++++++++++++++---------------
recipes/editline/editline_20100424-3.0.bb | 2 +-
8 files changed, 206 insertions(+), 205 deletions(-)
Diff: http://gitweb.openembedded.net/?p=openembedded.git/?a=commitdiff;h=2fbd56c0ef7df1b45746dbf9390805f2e67c590b
More information about the Openembedded-commits
mailing list