Difference between revisions of "R and Calc: Bugs and Feature Requests"

Revision as of 20:28, 29 August 2007

This section is meant to keep track of the bugs plaguing the add-on, as well as any features people would like to see in upcoming versions. For now, there are three categories on this page:

• Bugs: things that need to be fixed urgently (ideally, in the next release).
• Feature Requests: things that need to be added at some point in the future, but are not necessary for the healthy functioning of the software.
• Implemented Requests: once anything in the categories above is implemented, it is moved here.

Bugs

• As it stands, RCalcCaller can't read values from matrices with equations. This code does not work =RTestConnection() with a value of 0 or 1, it will throw an error if we refer to this in code. For example, try the code below:

// First, type =RTestConnection() in cell A1.

a <- {$A1}

a*3

• RCalcCaller can't accept String inputs from cells.
• Need to implement missing values.
• The following code doesn't seem to work in the RCalcCoder on Windows XP SP2, R 2.5.1:

rnorm(1)

{$OUT#A1}<-{$BASE}

• Passing the following code to RCalcDump causes a NullPointerException:

nls(y ~ a*x + b, data = data.frame(cbind(x = c(1.1, 2.1, 3, 3.9), y = c(1, 2, 3, 4))), start=list(a = 1, b = 1))

This is likely because the returned R object has embedded REXPs, functions, and environments.

• Passing a<-127 to RCalcDump will cause it to print the outputs of the previous statement rather than this one.
• Passing the following code causes the RCalcCoder to crash:

3+3

{$OUT#C1}<-{$BASE}

• R optional packages must be installed in the default R location... Otherwise they cannot be loaded.
• The add-on needs to be installed manually -- Tools > Extension Manager fails to install properly.
• Very slow in extremely large sets of data (probably due to using TCP/IP to send information).

Feature Requests

• Dynamic array output. As it stands, you need to know the size of the array if you want the RCalcCoder to output properly.
• Need to implement error output -- right now, nothing happens. This applies to RCalcDump and RCalcCaller.
• Make it so the {$BASE} keyword can be replaced with code. Currently, RCalcCaller won't work with

{$OUT#A1}<-var(c(1,2,3,4)) But having such code support would be extremely useful.

• Make the actual syntax more intuitive and easier to use.
• The getOutputs() function in the RCalcInterface is very inefficient and should be replaced (note that this is a fairly substantial coding change).

Implemented Requests

None yet, this list was just put up. :)