Closed elfrances closed 7 months ago
Thanks for spotting the error in btlib. I've uploaded a fix. i have not changed the btferret example because prompt will be a valid string - the compiler cannot be expected to see it. You make a good point about the warnings.
Compilation of btferret following the instructions in the README results in the following two errors:
The fix is pretty straightforward, as shown by the diff's below:
And when compilation warnings are enabled, gcc prints lots of them, many related to mixing up pointers of different sign: e.g. "char " and "unsigned char ". I think it would be "a good thing" if the code could compile warning-free ...