search for: argument1

Hello, As prompted by B. Ripley (see below), I am transfering this over from R-User ... For a package I am writing a function that looks like test <- function(Argument1=NA){ # Prerequisite testing if(!(is.na(Argument1))){ if(!(is.character(Argument1))){ stop("Wrong class.") } } # Function Body cat("Hello World\n") } Documentation of this is straight forward: ... \usage{test(Argument1=NA)} ... However writing the function could be...

...Writing R Extensions manual says that one should describe each element of the argument list (which is afcourse OK) in a form: \item{arg_i}{Description of arg_i.} When I started with R it really helped me that some "man pages" used \item{arg_i}{Mode. Description of arg_i.} e.g. \item{argument1}{Logical. Bla bla bla.} \item{argument2}{Integer. Bla bla bla.} \item{argument2}{Character. Bla bla bla.} Although one can most of the time deduce from the man page what mode should each argument be, I belive that it would enhance redeability if mode specification would be mandatory. I would als...

...jax request. It makes it possible to send the success and failure functions information about the browser state when the call was made. Yahoo! UI user code looks like var callback = { success: function(o) {/*success handler code*/}, failure: function(o) {/*failure handler code*/}, argument: [argument1, argument2, argument3] } The example comes from http://developer.yahoo.com/yui/connection/#async Can this be done with Rails link_to_remote()? If not is there a workaround? Thanks, Peter

Hi, I noticed that when dial terminates it does not return to the dialplan, and therefore can not execute any entry after Dial(). Is there any trick to overcome this limitation ? How I am supposed to handle the returned vales DIALEDTIME, ANSWEREDTIME if I can not execute anything after Dial()? I made a workaround with DeadAGI (below) but it is unreliable: if 2 calls end

The changes to vorbisfile that I suggested earlier have now been committed - this is mostly a merge of my code with a similar patch from Martin Vogt (thanks Martin). The old ov_open() interface remains untouched - and for many people, this is all you'll need to use, ever. It now calls the new interface with appropriate arguments. The new ov_open_callbacks() function adds an extra argument to

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on native

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on native

This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect call into in-place execution or direct call. The first patch imports helper functions which themselves doesn't interesting things. The second patch replaces the indirect function calls with a

This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect call into in-place execution or direct call. The first patch imports helper functions which themselves doesn't interesting things. The second patch replaces the indirect function calls with a