source and textConnection

Is this warning given on purpose?
myconn<-textConnection("print(11*11)")
source(myconn)
[1] 121
Warning message:
In source(myconn) : argument 'encoding = "native.enc"' will be ignored

Could it be omitted, since the docs state that encoding is only use if
the corresponding argument is a file name or url?
Erich Neuwirth, University of Vienna
Faculty of Computer Science
Computer Supported Didactics Working Group
Visit our SunSITE at http://sunsite.univie.ac.at
Phone: +43-1-4277-39464 Fax: +43-1-4277-39459
Using todays freshly downloaded compiled version of R-2.10.0 beta
let me pose this question once again:
myconn<-textConnection("print(11*11)")
source(myconn)
produces
[1] 121
Warning message:
In source(myconn) : argument 'encoding = "native.enc"' will be ignored
So I get a warning about a default parameter value I did not use myself.
This is somewhat strange.
Up to 2.9.2 this warning did not show up,
and 2.9.2 also has the encoding parameter.

source(myconn,encoding="unknown")
does not produce a warning.

Will it remain like this?
I am asking because then I have to adapt a certain mechanism in RExcel.
Erich Neuwirth, University of Vienna
Faculty of Computer Science
Computer Supported Didactics Working Group
Visit our SunSITE at http://sunsite.univie.ac.at
Phone: +43-1-4277-39464 Fax: +43-1-4277-39459
Using todays freshly downloaded compiled version of R-2.10.0 beta
let me pose this question once again:

myconn<-textConnection("print(11*11)")
source(myconn)
produces
[1] 121
Warning message:
In source(myconn) : argument 'encoding = "native.enc"' will be ignored
So I get a warning about a default parameter value I did not use myself.
This is somewhat strange.
Up to 2.9.2 this warning did not show up,
and 2.9.2 also has the encoding parameter.

source(myconn,encoding="unknown")
does not produce a warning.

Will it remain like this?
I am asking because then I have to adapt a certain mechanism in RExcel.

I think this is a bug, but it may not be serious enough to fix during 
code freeze, so there's a good chance it will remain in 2.10.0, but 
hopefully not in later releases.

I'll take a look today.

Duncan Murdoch
Using todays freshly downloaded compiled version of R-2.10.0 beta
let me pose this question once again:

myconn<-textConnection("print(11*11)")
source(myconn)
produces
[1] 121
Warning message:
In source(myconn) : argument 'encoding = "native.enc"' will be ignored
So I get a warning about a default parameter value I did not use myself.
This is somewhat strange.
Up to 2.9.2 this warning did not show up,
and 2.9.2 also has the encoding parameter.

source(myconn,encoding="unknown")
does not produce a warning.

Will it remain like this?
I am asking because then I have to adapt a certain mechanism in RExcel.

I spent a little time looking into this yesterday, and it appears to 
have shown up quite a while ago (it was there in July builds, for 
instance).  I will eventually track it down, but certainly not for 2.10.0.

Generally bugs are easier to find when they're fresh, which is why we 
ask people to try out the R-devel builds.  In this case, it's obvious 
how to fix the bug, but I'd rather not do that until I see what the 
change that caused it was intended to do:  I don't want to undo that.

Duncan Murdoch
On 10/22/2009 7:21 AM, Erich Neuwirth wrote:
Using todays freshly downloaded compiled version of R-2.10.0 beta
let me pose this question once again:

myconn<-textConnection("print(11*11)")
source(myconn)
produces
[1] 121
Warning message:
In source(myconn) : argument 'encoding = "native.enc"' will be ignored
So I get a warning about a default parameter value I did not use myself.
This is somewhat strange.
Up to 2.9.2 this warning did not show up,
and 2.9.2 also has the encoding parameter.

source(myconn,encoding="unknown")
does not produce a warning.

Will it remain like this?
I am asking because then I have to adapt a certain mechanism in RExcel.

I spent a little time looking into this yesterday, and it appears to 
have shown up quite a while ago (it was there in July builds, for 
instance).  I will eventually track it down, but certainly not for 2.10.0.
Nothing is certain.  I found that this warning came from something I 
introduced in May; it appears to me to be in the class of trivial bugs 
that the development guidelines allow to be fixed now.  So I've 
committed the change to the 2.10.0 branch.

Duncan Murdoch
Generally bugs are easier to find when they're fresh, which is why we 
ask people to try out the R-devel builds.  In this case, it's obvious 
how to fix the bug, but I'd rather not do that until I see what the 
change that caused it was intended to do:  I don't want to undo that.

Duncan Murdoch

______________________________________________
R-devel at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel