diff options
author | Chris Larson <chris_larson@mentor.com> | 2010-02-25 09:42:28 -0700 |
---|---|---|
committer | Richard Purdie <rpurdie@linux.intel.com> | 2010-03-22 15:02:59 +0000 |
commit | 57044b9a6240235a403eac4067e2e2113e03b6eb (patch) | |
tree | 46f15cb768778aa0f8363d6da2e98c6aaa69aadb /bitbake/lib/bb/msg.py | |
parent | ada2a8494a88b59de25c0a44fce30190f560eff4 (diff) | |
download | openembedded-core-57044b9a6240235a403eac4067e2e2113e03b6eb.tar.gz openembedded-core-57044b9a6240235a403eac4067e2e2113e03b6eb.tar.bz2 openembedded-core-57044b9a6240235a403eac4067e2e2113e03b6eb.tar.xz openembedded-core-57044b9a6240235a403eac4067e2e2113e03b6eb.zip |
Implement ??= operator
??= is a lazy, conditional assignment. Whereas a ?= immediately assigns to
the variable if the variable has not yet been set, ??= does not apply the
default assignment until the end of the parse. As a result, the final ??= for
a given variable is used, as opposed to the first as in ?=.
Note that the initial implementation relies upon finalise() to apply the
defaults, so a "bitbake -e" without specifying a recipe will not show the
defaults as set by ??=. Moving application of the default into getVar adds
too large a performance hit. We may want to revisit this later.
(Bitbake rev: 74f50fbca194c9c72bd2a540f4b9de458cb08e2d)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Diffstat (limited to 'bitbake/lib/bb/msg.py')
0 files changed, 0 insertions, 0 deletions