Am 23.10.2018 um 20:11 schrieb Allin
On Tue, 23
Oct 2018, Sven Schreiber wrote:
Is there any other incarnation of the
problem apart from this lags thing?
I'm pretty sure there isn't. Maybe we should just confine the
diagnostic to the case where a function and series share a name,
and we come across an instance of "shared_name(". As things stand
the function will be called by preference in this case: it might
or might not work in context, and might or might not be what the
user actually wants, so perhaps this should be an error rather
than just a warning.
In the context of being inside a function (package) I think the
identifier/series should have the preference: Because for those only
the local scope applies, and it would be foolish by the author to
choose an identifier with the same name as an external function she
wants to call. So the intent would point to the identifier.
(I guess it may become more complicated if returning a list is
concerned where possibly the name of the member series is dictated
by external demands as well...)
OTOH, if we're not inside a function (global or session scope) the
other preference may be more appropriate.
And AFAICS this only applies to right-hand side expressions in a
genr context, no? I mean if a line starts with "shared_name(", it
must be a function call I think.
It's a bit of a mess, really. That's what scoping rules are for, I