[Rd] Unexpected argument-matching when some are missing

Emil Bode emil@bode @ending from d@n@@kn@w@nl
Fri Nov 30 17:17:48 CET 2018

But the main point is where arguments are mixed together:

> debugonce(plot.default)
> plot(x=1:10, y=, 'l')
Browse[2]> missing(y)
Browse[2]> y
[1] "l"
Browse[2]> type
[1] "p"

I think that's what I fall over mostly: that named, empty arguments behave entirely different from omitting them (", ,")

And I definitely agree we need a guru to explain it all to us (

Cheers, Emil Bode

On 30/11/2018, 15:35, "S Ellison" <S.Ellison using LGCGroup.com> wrote:

    > Yes, I think all of that is correct. But y _is_ missing in this sense:
    > > plot(1:10, y=)
    > > ...
    > Browse[2]> missing(y)
    Although I said what I meant by 'missing' vs 'not present', it wasn't exactly what missing() means. My bad.
    missing() returns TRUE if an argument is not specified in the call _whether or not_ it has a default, hence the behaviour of missing(y) in debug(plot).
    But we can easily find out whether a default has been assigned:
    plot(1:10, y=, type=)
    Browse[2]> y
    Browse[2]> type
    ... which is consistent with silent omission of 'y=' and 'type=' 
    Still waiting for a guru...
    Steve E
    This email and any attachments are confidential. Any use, copying or
    disclosure other than by the intended recipient is unauthorised. If 
    you have received this message in error, please notify the sender 
    immediately via +44(0)20 8943 7000 or notify postmaster using lgcgroup.com 
    and delete this message and any copies from your computer and network. 
    LGC Limited. Registered in England 2991879. 
    Registered office: Queens Road, Teddington, Middlesex, TW11 0LY, UK

More information about the R-devel mailing list