search for: _always

Hi all Sorry for the confusing title. I noticed the following inconsistency: If i have a function that returns a named list with 2 (or more) elements, then using 'vapply' retains the names of the elements: > vapply(1:3, function(x) list("foo" = "bar", "hello" = "world"), > vector("list", 2)) [,1] [,2] [,3] foo

...s at r-project.org] On Behalf Of Dean Attali > If i have a function that returns a named list with 2 (or more) elements, > then using 'vapply' retains the names of the elements: > .... > But if the function only returns one element, then the name "foo" is lost vapply _always simplifies_ according to the documentation. In the first case (function return value contains more than one element, and each ), vapply simplifies to a matrix of two lists (!). The names "foo" and "hello" have been added to the dimnames so you can tell which is which. in the...

Quote---------------- > If i have a function that returns a named list with 2 (or more) elements, > then using 'vapply' retains the names of the elements: > .... > But if the function only returns one element, then the name "foo" is lost vapply _always simplifies_ according to the documentation. In the first case (function return value contains more than one element, and each ), vapply simplifies to a matrix of two lists (!). The names "foo" and "hello" have been added to the dimnames so you can tell which is which. in the...

...ppropriate, i.e., whether anyone needs the current -m behaviour. It looks to me like one would need to change mailbox_open_or_create_synced() if (box != NULL || no_mailbox_autocreate) return box; to something like (assuming an enum mailbox_autocreate {_never,_inbox,_always} if (box != NULL) return box; if (mailbox_autocreate == mailbox_autocreate_never || strcasecmp (mailbox, "INBOX") != 0) return NULL;

...he bottom of this case, PLASE let me know what else you still need. >I have mentioned this more than once already. There must be >_matching_ values between the MBR / partition table / VBR. Hummm... I had to go a Googling' to find out what "VBR" stands for. But now I know. (I _always knew that there was _something_ special at the start of every partition, but I never knew what it was called until now.) >For example, if the first partition starting offset is 63 sectors, >the partition table should have CHS values that correspond to LBA 63. I _think_ that I _perhaps_ un...

> With respect to all of the actually important stuff however, I may have > missed it all, but I don't recall having read or seen an explanation of > what Ady & everybody else finally figured out about all this. What is > the answer, in the end? I did get the part about how (for my board, > at least) tweeking some of the info within the relevant MBR partition > table