01-16-2025, 12:35 AM
liberty basic sort of worked this way to provide graphics functions from the win32 api.
otherwise this would be quite inefficient. usb drives are very slow, including the 3.2 ones. i have had lousy experiences with anything version 3. one was supposed to give good performance but it became a lemon. i almost have to throw it away. what's the use of cheap storage if it's unreliable and it takes hours only to copy one gigabyte?
besides, we now have _readfile$ and _writefile. there's a way to use a vls as buffer, then map it out into a _mem variable and do the "pointer" arithmetic in memory. if it requires too much ram, then do the arithmetic using get/put, lof() and other such statements of binary file access.
otherwise this would be quite inefficient. usb drives are very slow, including the 3.2 ones. i have had lousy experiences with anything version 3. one was supposed to give good performance but it became a lemon. i almost have to throw it away. what's the use of cheap storage if it's unreliable and it takes hours only to copy one gigabyte?
besides, we now have _readfile$ and _writefile. there's a way to use a vls as buffer, then map it out into a _mem variable and do the "pointer" arithmetic in memory. if it requires too much ram, then do the arithmetic using get/put, lof() and other such statements of binary file access.