search for: dromedari

Hi all, How do I obtain the current active path of a function that's being called? That's to say, I have several source files and they all contain definition of function A. I would like to figure out which function A and from which file is the one that's being called and is currently active? Thanks a lot! [[alternative HTML version deleted]]

...und has no default value in above. > It behaves exactly like current get does if value.if.not.found > is not specified, and if it is specified, it would be faster > in the common situation mentioned below: > if(exists(x,...)) { get(x,...) } > > John > > P.S. if you like dromedaries call it valueIfNotFound ... > > .............................................................. > John P. Nolan > Math/Stat Department > 227 Gray Hall, American University > 4400 Massachusetts Avenue, NW > Washington, DC 20016-8050 > > jpnolan at american.edu...

In November, we had a "bug repository conversation" with Peter Hagerty and myself: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16065 where the bug report title started with --->> "exists" is a bottleneck for dispatch and package loading, ... Peter proposed an extra simplified and henc faster version of exists(), and I commented > --- Comment #2

...lue) } Note that value.if.not.found has no default value in above. It behaves exactly like current get does if value.if.not.found is not specified, and if it is specified, it would be faster in the common situation mentioned below: if(exists(x,...)) { get(x,...) } John P.S. if you like dromedaries call it valueIfNotFound ... .............................................................. John P. Nolan Math/Stat Department 227 Gray Hall, American University 4400 Massachusetts Avenue, NW Washington, DC 20016-8050 jpnolan at american.edu voice: 202.885.3140 web: aca...

...nd has no default value in above. > It behaves exactly like current get does if value.if.not.found > is not specified, and if it is specified, it would be faster > in the common situation mentioned below: > if(exists(x,...)) { get(x,...) } > > John > > P.S. if you like dromedaries call it valueIfNotFound ... > > .............................................................. > John P. Nolan > Math/Stat Department > 227 Gray Hall, American University > 4400 Massachusetts Avenue, NW > Washington, DC 20016-8050 > > jpnolan at american...

...e. >> It behaves exactly like current get does if value.if.not.found >> is not specified, and if it is specified, it would be faster >> in the common situation mentioned below: >> if(exists(x,...)) { get(x,...) } >> >> John >> >> P.S. if you like dromedaries call it valueIfNotFound ... >> >> .............................................................. >> John P. Nolan >> Math/Stat Department >> 227 Gray Hall, American University >> 4400 Massachusetts Avenue, NW >> Washington, DC 20016-8050 >>...

...ly -- I had originally also thought of returning the two parts explicitly, but then tended to prefer the version that behaved exactly like get() in the case the object is found. ... Nice interesting ideas! ... let the proposals and consideration flow ... Martin > John > P.S. if you like dromedaries call it valueIfNotFound ... :-) ;-) I don't .. as I said above, I already strongly dislike more than one hump. [ Each capital is one key stroke ("Shift") more , and each "_" is two key strokes more on most key boards..., and I do like identifiers that I can also qu...

...ly like current get does if value.if.not.found >>> is not specified, and if it is specified, it would be faster >>> in the common situation mentioned below: >>> if(exists(x,...)) { get(x,...) } >>> >>> John >>> >>> P.S. if you like dromedaries call it valueIfNotFound ... >>> >>> .............................................................. >>> John P. Nolan >>> Math/Stat Department >>> 227 Gray Hall, American University >>> 4400 Massachusetts Avenue, NW >>> Washing...

Won't it be better to have a convention that allows lowercase, dash, underscore and dot as only valid characters for new package names and keep the ancient format validation scheme for older package names? This could be implemented by a single function, taking a strictNaming_b_1 parameter which defaults to true. Easy to use, and compliance results will vary according to the parameter value,