Hi Jen,
This was already resolved for R 3.5.1 by just disabling buffering on
terminal file connections like stdin.
Sounds like you might want to be running a web service or something
instead though.
Michael
On Tue, Jun 12, 2018 at 4:46 PM, Jennifer Lyon
wrote:
> Hi:
>
> I have also just stumbl
Hi:
I have also just stumbled into this bug. Unfortunately, I can not
change the data my program receives from stdin. My code runs in a
larger system and stdin is sent to a Docker container running my R
code. The protocol is I read a line, readLines("stdin", n=1), do some
actions, send output on s
Martin, et al.,
> I think we should allow 'year' to be "double" instead, and so it
> could also be +Inf or -Inf and we'd nicely cover
> the conversions from and to 'numeric' -- which is really used
> internally for dates and date-times in POSIXct.
storing years as a double makes me worry slight
On Tue, Jun 12, 2018 at 6:28 PM, Martin Maechler wrote:
>
> I think we should allow 'year' to be "double" instead, and so it
> could also be +Inf or -Inf and we'd nicely cover
> the conversions from and to 'numeric' -- which is really used
> internally for dates and date-times in POSIXct.
>
> Ma
> Emil Bode
> on Tue, 12 Jun 2018 12:00:42 + writes:
> I agree that calling it invalid is a bit confusing, but I’m not sure what the
> wording should be, as the problem is that the conversion to POSIXlt is
> failing.
> The best solution would be to extend the whole POSIXlt-class
I agree that calling it invalid is a bit confusing, but I’m not sure what the
wording should be, as the problem is that the conversion to POSIXlt is failing.
The best solution would be to extend the whole POSIXlt-class, but that’s too
much work.
I’ve done some experiments, and it also seems that
