On Sun, Dec 4, 2011 at 8:07 PM, Jeff Newmiller wrote:
> I prefer to think of namespaces as preventing clashes with similarly-named
> functions in the main workspace or in other packages that might serve a
> different need.
>
> Given that purpose, I don't think I would have confined that particul
I prefer to think of namespaces as preventing clashes with similarly-named
functions in the main workspace or in other packages that might serve a
different need.
Given that purpose, I don't think I would have confined that particular
function behind the namespace, because any other use of that
On Sun, Dec 4, 2011 at 6:57 PM, Rolf Turner wrote:
>
> See end of message.
>
>
> On 05/12/11 10:19, Erin Hodgess wrote:
>>
>> Dear R People:
>>
>> If I put in:
>>
>>> findPerl
>>
>> Error: object 'findPerl' not found
>>
>>
>> But if I use:
>>
>>> gdata:::findPerl
>>
>> function (perl, verbose = "F
See end of message.
On 05/12/11 10:19, Erin Hodgess wrote:
Dear R People:
If I put in:
findPerl
Error: object 'findPerl' not found
But if I use:
gdata:::findPerl
function (perl, verbose = "FALSE")
{
errorMsg<- "perl executable not found. Use perl= argument to
specify the correct p
??namespace
?getAnywhere
?"::"
See also: http://www.stat.uiowa.edu/~luke/R/namespaces/morenames.pdf
Bottom line: namespaces provide a mechanism to "hide" certain
variables within a package. Special measures as documented above are
required to view them
-- Bert
On Sun, Dec 4, 2011 at 1:19 PM,
Dear R People:
If I put in:
> findPerl
Error: object 'findPerl' not found
But if I use:
> gdata:::findPerl
function (perl, verbose = "FALSE")
{
errorMsg <- "perl executable not found. Use perl= argument to
specify the correct path."
if (missing(perl)) {
perl = "perl"
}
6 matches
Mail list logo