search for: fvprintf

...call. >>>> >>> >>> That's likely because you aren't writing enough to actually trigger a write to disk during the write. Writes are buffered, and the error doesn't happen >>> until the buffer is written. >> I can confirm this behavior with fvprintf(). Small and medium sized writings >> on /dev/full don't trigger error and 1MB does. >> >> But if fprintf() is used, it returns a negative value from the very first byte written. > I correct myself. In my test, fprintf() returned -1 for another reason (connection was alread...

...values >> returned by the vfprintf call. >> > > That's likely because you aren't writing enough to actually trigger a write to disk during the write. Writes are buffered, and the error doesn't happen until > the buffer is written. I can confirm this behavior with fvprintf(). Small and medium sized writings on /dev/full don't trigger error and 1MB does. But if fprintf() is used, it returns a negative value from the very first byte written. Serguei. > The regression test I put in had this problem; I'm working on MacOS and Windows, so I never got to act...

...s likely because you aren't writing enough to actually >>>>> trigger a write to disk during the write. Writes are buffered, >>>>> and the error doesn't happen >>>>> until the buffer is written. >>>> I can confirm this behavior with fvprintf(). Small and medium sized >>>> writings >>>> on /dev/full don't trigger error and 1MB does. >>>> >>>> But if fprintf() is used, it returns a negative value from the very >>>> first byte written. >>> I correct myself. In my t...

...rned by the vfprintf call. >>> >> >> That's likely because you aren't writing enough to actually trigger a write to disk during the write. Writes are buffered, and the error doesn't happen >> until the buffer is written. > I can confirm this behavior with fvprintf(). Small and medium sized writings > on /dev/full don't trigger error and 1MB does. > > But if fprintf() is used, it returns a negative value from the very first byte written. I correct myself. In my test, fprintf() returned -1 for another reason (connection was already closed at this...

...>> >>>> >>>> That's likely because you aren't writing enough to actually trigger a write to disk during the write. Writes are buffered, and the error doesn't happen >>>> until the buffer is written. >>> I can confirm this behavior with fvprintf(). Small and medium sized writings >>> on /dev/full don't trigger error and 1MB does. >>> >>> But if fprintf() is used, it returns a negative value from the very first byte written. >> I correct myself. In my test, fprintf() returned -1 for another reason (conne...

...se you aren't writing enough to actually >>>>>> trigger a write to disk during the write. Writes are buffered, >>>>>> and the error doesn't happen >>>>>> until the buffer is written. >>>>> I can confirm this behavior with fvprintf(). Small and medium sized >>>>> writings >>>>> on /dev/full don't trigger error and 1MB does. >>>>> >>>>> But if fprintf() is used, it returns a negative value from the very >>>>> first byte written. >>>> I c...

...to actually >>>>>>>> trigger a write to disk during the write. Writes are buffered, >>>>>>>> and the error doesn't happen >>>>>>>> until the buffer is written. >>>>>>> I can confirm this behavior with fvprintf(). Small and medium sized >>>>>>> writings >>>>>>> on /dev/full don't trigger error and 1MB does. >>>>>>> >>>>>>> But if fprintf() is used, it returns a negative value from the very >>>>>>>...

...t writing enough to actually >>>>>>> trigger a write to disk during the write. Writes are buffered, >>>>>>> and the error doesn't happen >>>>>>> until the buffer is written. >>>>>> I can confirm this behavior with fvprintf(). Small and medium sized >>>>>> writings >>>>>> on /dev/full don't trigger error and 1MB does. >>>>>> >>>>>> But if fprintf() is used, it returns a negative value from the very >>>>>> first byte written....

I tried the newest patch, but it does not seem to work for me (on Linux). Despite the check in Rconn_printf, the write.csv happily writes to /dev/full and does not report an error. When I added a printf("%d\n", res); to the Rconn_printf() definition, I see only positive values returned by the vfprintf call. Cheers, j. On 4 July 2017 at 21:37, Duncan Murdoch <murdoch.duncan at