On 01/01/2016 12:42 PM, Michael Palimaka wrote:
> I don't see the absurdity.
Two formally independent statements that are actually dependent because
of some implicit shared state:
>>
>> src_configure() {
>> local mycmakeargs=(
>> ...
>> )
>> cmake-utils_src_configure
>> }
>>
In this example it's clear that the behavior of ecmake depends on the
value of $myconf:
>>
>> src_configure() {
>> local myconf=(
>> ...
>> )
>> ecmake "${myconf[@]}"
>> }
>>
The latter is a lot more peaceful to maintain. I can hop right into the
code and see that changing $myconf is going to have some effect on the
ecmake line. In the first example, I could change $mycmakeargs 100 lines
away for some unrelated issue. The only way for me to know that it would
effect the cmake-utils_src_configure line is to read the source of that
function proactively (or after it breaks).
