It's exactly what I am doing. Log file "common" to respective machine logs "specific". Thinking about it, I am just using a for/next loop to search open files in use. But using the for value as the file open number. I am going to change the open handle to the safer FREEFILE function. All output handles are in the arrray I am searching for filenames. So the value of the handle does not have to be known. Only stored for look up.
|
Cautionary tale of open, append, close
|
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
Cautionary tale of open, append, close - by doppler - 01-14-2025, 03:28 PM
RE: Cautionary tale of open, append, close - by mdijkens - 01-15-2025, 09:40 PM
RE: Cautionary tale of open, append, close - by mdijkens - 01-15-2025, 09:48 PM
RE: Cautionary tale of open, append, close - by doppler - 01-16-2025, 10:23 AM
|
| Possibly Related Threads… | |||||
| Thread | Author | Replies | Views | Last Post | |
| Mix mode input of a binary open file Question! | doppler | 5 | 1,476 |
11-28-2024, 03:06 PM Last Post: Petr |
|
| qb64 "OPEN" linux /dev/ devices | Parkland | 2 | 787 |
06-30-2024, 02:52 AM Last Post: DSMan195276 |
|
| Suggestion: Preallocated file open | doppler | 14 | 2,753 |
02-25-2024, 02:35 AM Last Post: SMcNeill |
|
| Disco fails to open | Richard | 4 | 1,200 |
04-20-2022, 12:41 PM Last Post: admin |
|
Users browsing this thread: 1 Guest(s)

