Unless I misunderstood the post, QBasic / QB64 has always acted in this manner. I'll have a talk with our mail room, memo division.
Basically, LINE INPUT inputs the line up to the carriage return and since we are working with a sequential file here, that index place is maintained in memory; therefore, the next line input statements turns out the next line of text up to the next carriage return.
Now if you ever use binary, you have two choices. You can use LINE INPUT in QB64 only (not QBasic) with open for binary. It's faster, and works the same as a sequential read, but you can use it with get to input the entire text file at once. Of course then, you have to parse it if you want to read it line by line. I use the latter method in my WP routines.
Pete
Basically, LINE INPUT inputs the line up to the carriage return and since we are working with a sequential file here, that index place is maintained in memory; therefore, the next line input statements turns out the next line of text up to the next carriage return.
Now if you ever use binary, you have two choices. You can use LINE INPUT in QB64 only (not QBasic) with open for binary. It's faster, and works the same as a sequential read, but you can use it with get to input the entire text file at once. Of course then, you have to parse it if you want to read it line by line. I use the latter method in my WP routines.
Pete