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 /recipes/editline | |
| 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 'recipes/editline')
| -rw-r--r-- | recipes/editline/editline_20100424-3.0.bb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/recipes/editline/editline_20100424-3.0.bb b/recipes/editline/editline_20100424-3.0.bb index 9f9686b9ee..ff5a7e5b34 100644 --- a/recipes/editline/editline_20100424-3.0.bb +++ b/recipes/editline/editline_20100424-3.0.bb @@ -20,6 +20,6 @@ ENABLE_WIDEC[type] = "boolean" EXTRA_OECONF += "\ --with-gnu-ld \ - ${@oe.utils.ifelse(oe.types.value('ENABLE_WIDEC', d), \ + ${@oe.utils.ifelse(oe.data.typed_value('ENABLE_WIDEC', d), \ '--enable-widec', '')} \ " |