-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Small typo in 'afterburner.c' #63
Comments
Thanks for the report. It should be now fixed. See commit 0761907 |
Hi, thanks for the fix. I have now tried the following change. It works on Windows. I don't have a Linux system to test it with.
In your code I keep noticing the inconsistent use of the '0' value. This contradicts the rules of C/C++ syntax and the program is also more difficult to understand for co-programmers. Even if it technically works. 0 is the value zero for a numeric variable. e.g. in afterburner.c
should be
or in serial_port.h
should be
because guessedSerialDevice is a char array that should then be initialized like this:
Greetings |
I forgot to comment the line
verbose is used in the program as a pure YES/NO flag. So verbose doesn't actually contain a character as a value. For better understanding, it is a Boolean variable that only has the two values true and false.
This also applies to functions that you declared as char, which only return 0 or 1 as a result for successful or failed.
Greetings |
Very good comments! While adding them to my local files, I found the following bug: |
In line 188 in the printHelp() function the serial baud rate used is incorrectly specified.
The help text says 38400 but the code uses 57600.
In addition in printHelp(), the default device (if no -d 'device' option is specified) is not always COM1 (on Windows), but the highest COM number found (since the extension in serial_port.h).
Hubert
The text was updated successfully, but these errors were encountered: