search for: ceron

I am not sure if this is a bug or not. Gabor On Wed, Aug 12, 2015 at 11:51 AM, Luca Cerone <luca.cerone at gmail.com> wrote: > Following up on this, should I report a bug? can you drive me through > the process? > > Cheers, > Luca > > On Thu, Aug 6, 2015 at 4:55 PM, William Dunlap <wdunlap at tibco.com> wrote: >>>> Just a quick question: what...

...gt; c(One=1, Two=2)[[2]] [1] 2 > c(One=1, Two=2)[2] Two 2 (and [[ will only return 1 item, unlike [). Bill Dunlap TIBCO Software wdunlap tibco.com On Thu, Aug 6, 2015 at 5:36 AM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > On Thu, Aug 6, 2015 at 6:30 AM, Luca Cerone <luca.cerone at gmail.com> wrote: > [...] > > Just a quick question: what's the difference between `[.Date` and > `[[.Date`? > > Is it supposed to be the method for accessing the value right? > > For Dates and atomic vectors in general they are the same, but in &...

...quot;for". > > Interestingly, lapply and co. do consider the class: > > invisible(lapply(seq(d1, d2, by = 1), print)) > > works as you would expect. (The invisible() is to suppress printing > the return value.) > > Gabor > > On Thu, Aug 6, 2015 at 3:24 AM, Luca Cerone <luca.cerone at gmail.com> wrote: >> Dear all, >> I am experiencing a weird issue when iterating through dates in R >> (3.1.2 and 3.2.1 on 64bit linux machines) >> >> I am bit surprised about the behaviour of this snippet of code: >> >> d1 <- as.D...

...y=1) to character, so it's no longer a Date. The fact that Sys.Date() and as.character(Sys.Date()) both *print* the same thing does not mean they are the same. for ( dt in as.character(seq(d1,d2, by=1)) ) { print(dt) } Best, Josh > Gabor > > On Wed, Aug 12, 2015 at 11:51 AM, Luca Cerone <luca.cerone at gmail.com> wrote: >> Following up on this, should I report a bug? can you drive me through >> the process? >> >> Cheers, >> Luca >> >> On Thu, Aug 6, 2015 at 4:55 PM, William Dunlap <wdunlap at tibco.com> wrote: >>>>...

Dear all, I am experiencing a weird issue when iterating through dates in R (3.1.2 and 3.2.1 on 64bit linux machines) I am bit surprised about the behaviour of this snippet of code: d1 <- as.Date('2015-01-01') d2 <- as.Date('2015-01-31') for ( dt in seq(d1,d2, by=1) ) { dt <- as.character(dt) print(dt) } for ( dt in as.character(seq(d1,d2, by=1)) ) { print(dt) }

...this is a bug, at least in the documentation of ?"for". Interestingly, lapply and co. do consider the class: invisible(lapply(seq(d1, d2, by = 1), print)) works as you would expect. (The invisible() is to suppress printing the return value.) Gabor On Thu, Aug 6, 2015 at 3:24 AM, Luca Cerone <luca.cerone at gmail.com> wrote: > Dear all, > I am experiencing a weird issue when iterating through dates in R > (3.1.2 and 3.2.1 on 64bit linux machines) > > I am bit surprised about the behaviour of this snippet of code: > > d1 <- as.Date('2015-01-01') &g...

I'm trying to build a hack to add/modify a groupmap entry in the group_mapping.tdb file by hand. What I'd like to do is to manually perform something like this: echo -e "open group_mapping.tdb\ninsert my_key my_value\nq" | tdbtool In this attempt, I expect to add a new group map entry in the tdb file. The key I'm using is the same as samba uses: domain_group/SID. I'm