Welcome Guest. Please Login or Register. Apr 1st, 2018, 03:37am
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. We apologize Conforums does not have any export functions to migrate data. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
Thank you Conforums members.
Speed up Liberty BASIC programs by up to ten times!
Compile Liberty BASIC programs to compact, standalone executables!
Overcome many of Liberty BASIC's bugs and limitations!
Re: debug-yes;regular-no
« Reply #5 on: Dec 6th, 2017, 07:09am »
The problem was a little different to that described. The program did not END, it simply closed its window. I have not tested but I sssume LBB might behave the same way as LB. it hangs quietly in the background doing what it was instructed to do.
The problem was a little different to that described. The program did not END, it simply closed its window.
Ah, that is indeed very different. In that case the file will remain open indefinitely and there is no guarantee that data written with a PRINT# or PUT# will have been 'flushed' to the actual storage device (and thus be visible to, for example, another program looking at the same file).
In fact I might expect that LBB would, if anything, be more vulnerable to that possibility, because for performance reasons it stores output data in a temporary buffer which gets written only when full (or when the file is closed).
If you need to commit data to disk without closing the file there is a 'trick' you can use in LBB:
Code:
SEEK #file, LOC(#file)
Whilst you might expect that setting the file pointer to its current position would do nothing, it has the side-effect of flushing LBB's buffers.
Logged
