Skip to content

handle the return value of write()#810

Merged
uweseimet merged 1 commit intodevelopfrom
fix_x86_compiler
Aug 26, 2022
Merged

handle the return value of write()#810
uweseimet merged 1 commit intodevelopfrom
fix_x86_compiler

Conversation

@akuker
Copy link
Copy Markdown
Member

@akuker akuker commented Aug 26, 2022

With this change, I was able to build and run the feature_google_test tests on Ubuntu 22.

@uweseimet - would you be able to look at this? I don't have a way to test the printer functionality currently. But, it looks like a pretty benign change.

@akuker akuker requested a review from uweseimet August 26, 2022 01:56
@akuker akuker requested a review from erichelgeson as a code owner August 26, 2022 01:56
@uweseimet
Copy link
Copy Markdown
Contributor

uweseimet commented Aug 26, 2022

@akuker Looks fine to me. What was the error about? Anything related to the unused return value of write()?
Looking closer at the topic of this PR it must have been that ;-).

@uweseimet uweseimet merged commit c6da145 into develop Aug 26, 2022
@akuker
Copy link
Copy Markdown
Member Author

akuker commented Aug 26, 2022

@akuker Looks fine to me. What was the error about? Anything related to the unused return value of write()? Looking closer at the topic of this PR it must have been that ;-).

Ya, it was saying the return value of write() wasn't being used. Thank you for taking a look at this!

@akuker akuker deleted the fix_x86_compiler branch August 26, 2022 14:27
@uweseimet
Copy link
Copy Markdown
Contributor

It's good that you stumbled upon this issue, because regardless of the compiler complaining, returning false if there is a length mismatch is correct. Ignoring the write() result was a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants