Probably the split you are using. Before in the past I've had to do UBOUND(array)-1. And they can always look at the C++ code to see how it is delimited. I opted for Linux style which is CHR$(10) rather than Windows style which is CHR$(13) + CHR$(10).
Which split are you using? I've had issues before with splitting strings because of the algorithms that are out there. I haven't found one I really like just yet.
I opted for Linux style which is CHR$(10) rather than Windows style which is CHR$(13) + CHR$(10).
Oh is this built into the .h file? I approve! not that it matters :)
I consider the 2 byte delimiter the old DOS way and Chr$(10) the newer way, only 1 byte is more efficient.
Before in the past I've had to do UBOUND(array)-1
Don't you think this indicates an empty string on the end, I am wondering about a Chr$(0) on the end since C likes to do that. Anyway there is something useless at that Ubound.
Split1000 found here:
https://www.qb64.org/forum/index.php?topic=1607.msg108201#msg108201I am getting perfect counts in my tests of a simple array displayer and my arrays coming out of Split have some empty string character at Ubound of array. Maybe if I trimmed the returned string from pipecom? maybe I should just check that next, before the splitting. ;-))
It handles 0 and 1 base ReDim 'd arrays (dynamic that you can change the size of) it probably could handle an exotic
but I have enough things to test and play with.
I will show you the code when I am done messing with it. I am really interested in the ideal way to do files and folders cross platform. But I suspect ideal depends on the application as usual. So my app is get a filename or pathname from anywhere on hard drive. After that selecting multiple files from different folders for some operation like copy to SD drive maybe for my backups.