Possible bug in write strings

[Sergey]

Maybe I'm wrong, so correct me

Code: Select all

If OpenFile(0, "test.txt")
	FileSeek(0, Lof(0))
	Repeat
		WriteStringN(0, Str(ElapsedMilliseconds()))
		Delay(1000)	
	ForEver
; 	CloseFile(0)
Else
	MessageRequester("Error", "Can't open file!")
EndIf

If I run code in the debug mode and then kill the process the file has data
And If I run compiled executable file or run code without a debugger there are no strings in the file
Why?

And <ForEver> not hilighted in post


// Moved from "Bugs - Windows" to "Coding Questions" (Kiffi)

[mk-soft]

Programme is never terminated and the file buffer is not written.
Something like this should never be written !!!

[BarryG]

How can you run it when you've got "FileSeek(Lof(0))" without a file number? The code doesn't even compile.

[infratec]

Code: Select all

WriteStringN(0, Str(ElapsedMilliseconds()))
FlushFileBuffers(0)

Should do the trick.

[BarryG]

Maybe even using the #PB_File_NoBuffering flag with OpenFile().

[NicTheQuick]

Closing the file is essential to write every buffer persistently.

[Sergey]

Code: Select all

WriteStringN(0, Str(ElapsedMilliseconds()))
FlushFileBuffers(0)

Should do the trick.

Ha, it's work!

Thank you all for understanding

BarryG this is a test code of LOG file in case the system turns off unexpected
Yes, I need #PB_File_NoBuffering, cool!
Each time will learn something new in PureBasic

[Olli]

Code: Select all

WriteStringN(0, Str(ElapsedMilliseconds()))
FlushFileBuffers(0)

Should do the trick.

Thank you infratec. My suggest would have pushed on the shared i/o option in the OpenFile() arguments.

I note that the BarryG suggest seems to be safer, in the shut down ways.

[infratec]

For logging I always open with the flag #PB_File_Append (no FileSeek() needed) and close the file for each log entry.
Because then I can use tail

[idle]

What's faster in a multi writer senario
Keeping a file open appending and flush or open append close?

[Sergey]

What's faster in a multi writer senario
Keeping a file open appending and flush or open append close?

It all depends on the situation, in my case, the recording is made with many strings, so I chose a flush method
If there aren't so many strings, it's better to use closefile

[idle]

What's faster in a multi writer senario
Keeping a file open appending and flush or open append close?

It all depends on the situation, in my case, the recording is made with many strings, so I chose a flush method
If there aren't so many strings, it's better to use closefile

I'm interested in the latencies between the methods, especially from multiple threads, though it won't be hard to test but I haven't gotten to the stage where I'm focusing on writing to disk.

[Olli]

The worst thing, I have got on this theme of mass memory recording, is a total copy of all my file I wanted to copy to an USB key, with all my datas zeroed, after having unplugged, and then unplugged.