search for: gentleperson

Gentlepersons: A long time ago I used to be able to start R (version 2.6.1) from a Delphi 7 program and run a script by using a procedure like the following: function StartRAndWait (CommandLine : string) : Boolean; var Proc_info: TProcessInformation; Startinfo: TStartupInfo; ExitCode: longword;...

...:assertError(NN (1:3))# in all R versions ## # current R | new R ## # -----------|---------- class(getDataPart(m1)) # integer | numeric class(getDataPart(m2)) # integer | numeric In other words, with the above setting, the traditional gentleperson's agreement in S and R, __ "numeric" sometimes conveniently means "integer" or "double" __ will be slightly less often used ... which of course may be a very good thing. However, it breaks strict back compatibility also in cases where the previous behavior ma...

...| new R >> ## # -----------|---------- >> class(getDataPart(m1)) # integer | numeric >> class(getDataPart(m2)) # integer | numeric >> >> >> In other words, with the above setting, the traditional >> gentleperson's agreement in S and R, >> >> __ "numeric" sometimes conveniently means "integer" or "double" __ >> >> will be slightly less often used ... which of course may be a >> very good thing. >> >>...

...> > ## # current R | new R > ## # -----------|---------- > class(getDataPart(m1)) # integer | numeric > class(getDataPart(m2)) # integer | numeric > > > In other words, with the above setting, the traditional > gentleperson's agreement in S and R, > > __ "numeric" sometimes conveniently means "integer" or "double" __ > > will be slightly less often used ... which of course may be a > very good thing. > > However, it breaks strict back compatibility also in ca...

...# -----------|---------- >>>> class(getDataPart(m1)) # integer | numeric >>>> class(getDataPart(m2)) # integer | numeric >>>> >>>> >>>> In other words, with the above setting, the traditional >>>> gentleperson's agreement in S and R, >>>> >>>> __ "numeric" sometimes conveniently means "integer" or "double" __ >>>> >>>> will be slightly less often used ... which of course may be a >>>> very good thing. >&gt...

We do need an explicit method here, I think. The issue is that as() uses methods for the generic function coerce() but cannot use inheritance in the usual way (if it did, you would be immediately back with no change, since "integer" inherits from "numeric"). Copying in the general method for coercing to "numeric" as an explicit method for "integer" gives

...# -----------|---------- >>> class(getDataPart(m1)) # integer | numeric >>> class(getDataPart(m2)) # integer | numeric >>> >>> >>> In other words, with the above setting, the traditional >>> gentleperson's agreement in S and R, >>> >>> __ "numeric" sometimes conveniently means "integer" or "double" __ >>> >>> will be slightly less often used ... which of course may be a >>> very good thing. &gt...

...-----------|---------- >>>>> class(getDataPart(m1)) # integer | numeric >>>>> class(getDataPart(m2)) # integer | numeric >>>>> >>>>> >>>>> In other words, with the above setting, the traditional >>>>> gentleperson's agreement in S and R, >>>>> >>>>> __ "numeric" sometimes conveniently means "integer" or "double" __ >>>>> >>>>> will be slightly less often used ... which of course may be a >>>>> very g...

...## # -----------|---------- >>>> class(getDataPart(m1)) # integer | numeric >>>> class(getDataPart(m2)) # integer | numeric >>>> >>>> >>>> In other words, with the above setting, the traditional >>>> gentleperson's agreement in S and R, >>>> >>>> __ "numeric" sometimes conveniently means "integer" or "double" __ >>>> >>>> will be slightly less often used ... which of course may be a >>>> very good thing. >>&...