Parameter matching problem fix

[iwccsbfb]

This PR calls the function directly from input, not from the manual parameter matching. With the following test case, there might still be issues with parameter matching when matching which function to call.

But calling the function now won't cause any problem.

Here is the test case: library(lambda.r)

f1 (a = 1, ...) %as% {
    vs <- list(...)
    print(vs)
    NULL
}
f1(1, 2, 3)

before the change:

> library(lambda.r)
> f1 (a = 1, ...) %as% {
+     vs <- list(...)
+     print(vs)
+     NULL
+ }
> f1(1, 2, 3)
[[1]]
[1] 1

[[2]]
[1] 2

[[3]]
[1] 3

NULL

After the change:

> library(lambda.r)
> f1 (a = 1, ...) %as% {
+     vs <- list(...)
+     print(vs)
+     NULL
+ }
> f1(1, 2, 3)
[[1]]
[1] 2

[[2]]
[1] 3

NULL

[iwccsbfb]

Reference: https://cran.r-project.org/doc/manuals/R-lang.html#Argument-matching We can apply this parameter matching procedure:

1. Exact matching
2. Partial matching
3. Positional matching

[iwccsbfb]

There is bug. If there are unspecified default parameters, this would fail.