C to C++ migration and refactoring #17
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: xt-sys/exectos#17
Reference in New Issue
Block a user
Proposed changes
Agreements
@@ -0,0 +398,4 @@BOOLEANDebug::SerialPortReady(){return (BOOLEAN)(SerialPort.Flags & COMPORT_FLAG_INIT);Do we need to typecast each bool operation? In C this returned integer value and compiler knew how to cast it into our BOOLEAN enum. In C++, result value is of bool type that cannot be automatically typecasted into enum.
No, we do not have to. Alternatively, I can suggest moving the BOOLEAN type definition from xttypes.h to xtcompat.h:
This will allow us to maintain backward compatibility with C and get rid of explicit typecasts at the same time.
This should also work in the case of the quoted fragment, even though the result of the operation is not of type bool but int. The result of the expression will be 0 if the flag is not set, or the value of COMPORT_FLAG_INIT if it is. It is only the comparison of this result, for example (SerialPort.Flags & COMPORT_FLAG_INIT) != 0, that actually yields a bool type.
Please let me know if you accept this, then I will commit the proposed change.
You are right, this results in int, not bool. There are more such changes like this in the diff, and I added a comment to the first one, as its the only one that fits on first page. unfortunately. Never mind, I think the proposed solution will be OK.