Re: When file truncation happens by Basic's Open statement

Hi Andrew, On Fri, 21 Dec 2018 14:51:12 -0500, "Andrew Pitonyak" wrote: > > I evaluated the behavior from Basic for all of the different modes based on a > specific build on a specific Linux platform. I did not read the code, nor did > I test different platforms. I documented all of this in O

Re: When file truncation happens by Basic's Open statement

Hi Mike, On Fri, 21 Dec 2018 19:15:40 +, Kaganski Mike wrote: > > On 21.12.2018 20:37, Takeshi Abe wrote: (snip) >> "X": the runtime deletes the file of given path first if already exists; >> "-": it does not. >> (*) requested in i#18638 ; >

Re: When file truncation happens by Basic's Open statement

I evaluated the behavior from Basic for all of the different modes based on a specific build on a specific Linux platform. I did not read the code, nor did I test different platforms. I documented all of this in OOME on my web site. Don't remember the direct link, but, it is on http://www.piton

Re: When file truncation happens by Basic's Open statement

Hi! On 21.12.2018 20:37, Takeshi Abe wrote: > In order to tell whether the behavior reported in tdf#119102 [1] is a bug > or not, I would like to understand the specification of LibO Basic's Open > statement [2]. > > The following table summarizes what current (master) LibO does, which I read > f

When file truncation happens by Basic's Open statement

Hi, In order to tell whether the behavior reported in tdf#119102 [1] is a bug or not, I would like to understand the specification of LibO Basic's Open statement [2]. The following table summarizes what current (master) LibO does, which I read from SbiStream::Open() in basic/source/runtime/iosys.