Dan Zwell <dzwell@xxxxxxxxx> writes:
> Previously, the Git->repository()->config('non-existent.key')
> evaluated to as true in a vector context. Return an empty list
> instead.
> ---
> I don't know whether this breaks anything, because I don't use most of
> the git perl scripts. I can't imagine that there is a script that
> relies on the fact that config('non-existent.key') actually returns
> (''), in an array context. Is this a reasonable change?
I did not examine the callers but my gut feeling is that it
would be simpler and cleaner to always return () without
checking the context. In scalar context:
sub null {
...
return ();
}
my $scalar = null();
would assign undef to $scalar anyway.
I generally try to stay away from functions that changes their
return values depending on the context, because they tend to
make reading the callers to find bugs more difficult. An
exception is a function that tries to mimic a built-in operator,
because reading the callers to such a function, as long as it is
clear which built-in the function is imitating, can apply the
same knowledge on how the callee would behave you already have
by knowing Perl itself.
The same thing can be said about functions with prototypes to
force certain context on the caller's side. Avoid it unless
there is a good reason.
Maybe it is just me, but that's my reaction.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
