diff options
author | Björn Gustavsson <[email protected]> | 2014-11-03 12:12:30 +0100 |
---|---|---|
committer | Björn Gustavsson <[email protected]> | 2015-01-12 11:40:26 +0100 |
commit | 652767e7b8296296ef08294e001353fe304b964a (patch) | |
tree | 5dab1c1599e93e9135ec613274c19e9eb0cc2b09 /otp_build | |
parent | 5abac511937a99414902d3052fb633e1a65812d3 (diff) | |
download | otp-652767e7b8296296ef08294e001353fe304b964a.tar.gz otp-652767e7b8296296ef08294e001353fe304b964a.tar.bz2 otp-652767e7b8296296ef08294e001353fe304b964a.zip |
Clean up handling of 'simpletable' and 'componentrelation'
The constraint_member/2 function is used for looking up 'simpletable'
and 'componentrelation' constraints. Both parts of its name are
misleading. The "constraint" part makes you think that it is a general
function for constraints, but it is not - it can only search for
'simpletable' and 'componentrelation'. The "member" part makes you
think that it would return a boolean, but it returns either
{true,Tuple} or false, making it more similar to lists:keysearch/3.
Use lists:keyfind/3 (or lists:keymember/3) instead of
constraint_member/2. Also use lists:keyfind/3 in one place where
there was a direct matching of a 'simpletable' constraint.
Diffstat (limited to 'otp_build')
0 files changed, 0 insertions, 0 deletions