Re: [Rd] RFC: make as.difftime more consistent or convenient

2018-07-31 Thread dietmar.schindler
Hello! you, Emil Bode , wrote on Tuesday, July 31, 2018 1:55 PM: > Some of the changes you're proposing could be made (with effort), but note > that you're not > restricted to providing strings with a format. > What you're trying to do can be accomplished with as.difftime(12, > units='weeks'),

[Rd] RFC: make as.difftime more consistent or convenient

2018-07-31 Thread dietmar.schindler
Hello! I notice I can convert strings containing hour, minute or second specifications to a 'difftime': > as.difftime("12 h", "%H") Time difference of 12 hours > as.difftime("12 m", "%M") Time difference of 12 mins > as.difftime("12 s", "%S") Time difference of 12 secs But I can't do so with a

Re: [Rd] Bug report: POSIX regular expression doesn't match for somewhat higher values of upper bound

2017-04-10 Thread dietmar.schindler
> Von: Martin Maechler [mailto:maech...@stat.math.ethz.ch] > Gesendet: Mittwoch, 5. April 2017 11:15 > > > > > on Tue, 4 Apr 2017 08:45:30 + writes: > > > Dear Sirs, > > while > > >> regexpr('(.{1,2})\\1', 'foo') > > [1] 2 > > attr(,"match.length") > > [1]

[Rd] Bug report: POSIX regular expression doesn't match for somewhat higher values of upper bound

2017-04-04 Thread dietmar.schindler
Dear Sirs, while > regexpr('(.{1,2})\\1', 'foo') [1] 2 attr(,"match.length") [1] 2 attr(,"useBytes") [1] TRUE yields the correct match, an incremented upper bound in > regexpr('(.{1,3})\\1', 'foo') [1] -1 attr(,"match.length") [1] -1 attr(,"useBytes") [1] TRUE incorrectly yields no match. R v