search for: otherfunct

...ip] > Error in substr<-(*tmp*, 3, 4, value = "IS") : > unused argument(s) (value ...) Question: ======= Is there a reference to the obseravation, that in R, missing parameters of a function can be "declared" using NULL, as in xxx <- function (x, miss=NULL) { otherfunction <- function (x, missOther=NULL) { .. } otherfunction(x, miss) } The solution of R is preferable to S+3.4's, since it allows functions within functions to have missing parameters without the (ugly) construct: xxx <- function (x, miss) { otherfunction <- function (x, miss) { .....

...n and have discovered an interesting problem. I can call webservice functions just fine, as long as they do not require any arguments, but function that do require arguments do not work. The arguments are sent as either null or an empty string. My API has these method definitions: api_method :otherFunction, :expects=>[{:username=>:string}], :returns=>[:string] api_method :test, :returns=>[:int] Calling test works perfectly. When I try to call otherFunction from my controller, after setting up the soap_client: soap_client.otherFunction(''name'') Somehow the use...

On Mon, Mar 02, 2015 at 12:12:34AM -0500, John Criswell wrote: > On 3/2/15 12:07 AM, Haopeng Liu wrote: > >Got it, thanks. But in my pass, I use function name to locate. Can I > >disable mangling in clang? > > No, but you can probably fine a library that can either mangle the original > name or demangle the name you're seeing in the LLVM bitcode. > > As an FYI,

Peter Stuge wrote: > > Matthieu Hautreux wrote: >> The change proposed by Cyril in sftp is a very pragmatic approach to >> deal with parallelism at the file transfer level. It leverages the >> already existing sftp protocol and its capability to write/read file >> content at specified offsets. This enables to speed up sftp transfers >> significantly by