diff options
author | Chris Larson <chris_larson@mentor.com> | 2011-02-09 10:28:42 -0700 |
---|---|---|
committer | Chris Larson <chris_larson@mentor.com> | 2011-02-09 12:10:45 -0700 |
commit | 2fbd56c0ef7df1b45746dbf9390805f2e67c590b (patch) | |
tree | a549ae6d6eb2783e5d2390f4bb7e007af551464f /classes/typecheck.bbclass | |
parent | f41d2fdfa6fc443353aec43eec0bfdf5c4dbb5f8 (diff) | |
download | openembedded-2fbd56c0ef7df1b45746dbf9390805f2e67c590b.tar.gz |
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@mentor.com>
Diffstat (limited to 'classes/typecheck.bbclass')
-rw-r--r-- | classes/typecheck.bbclass | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/classes/typecheck.bbclass b/classes/typecheck.bbclass index 646cd4eed2..bacaad8691 100644 --- a/classes/typecheck.bbclass +++ b/classes/typecheck.bbclass @@ -3,10 +3,9 @@ # See oe.types for details. python check_types() { - import oe.types if isinstance(e, bb.event.ConfigParsed): for key in e.data.keys(): if e.data.getVarFlag(key, "type"): - oe.types.value(key, e.data) + oe.data.typed_value(key, e.data) } addhandler check_types |