Last active
September 22, 2020 17:30
-
-
Save iammattcoleman/793b5589fdb4eefe940662c4c7f90e41 to your computer and use it in GitHub Desktop.
RFC: libvirt coding style
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
virBufferAddLit(&query, CIM_DATAFILE_WQL_SELECT | |
"WHERE " | |
"Name='c:\\\\windows\\\\system32\\\\vmms.exe'"); |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
virBufferAddLit(&query, CIM_DATAFILE_WQL_SELECT "WHERE " | |
"Name='c:\\\\windows\\\\system32\\\\vmms.exe'"); |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
virBufferAddLit(&query, CIM_DATAFILE_WQL_SELECT | |
"WHERE Name='c:\\\\windows\\\\system32\\\\vmms.exe'"); |
I personally prefer option 3 too...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Assume there's an included header containing...
Which form is most readable to libvirt developers? I'd like my contributions to fit in with the rest of the codebase.
I prefer #3, but the second line is 82 characters.