{"push_id":2847540254,"size":10,"distinct_size":10,"ref":"refs/heads/master","head":"cb0497687e9ed8431d0b90b0ae1acbc8dfdf655f","before":"463da8090254f6077f30a8e5274dd6a5908bb2bc","commits":[{"sha":"a6f1211ee610ae95359848fc441241ed200c0114","author":{"name":"Stephen Heumann","email":"accfa2c3d6747a9e483bf951795ebb81992292dc@gmail.com"},"message":"Properly treat #line directive as giving the next line number, not the current one.","distinct":true,"url":"https://api.github.com/repos/byteworksinc/ORCA-C/commits/a6f1211ee610ae95359848fc441241ed200c0114"},{"sha":"9ff3407c60d9b3c57c2f49eb8c05d192fb64df56","author":{"name":"Stephen Heumann","email":"accfa2c3d6747a9e483bf951795ebb81992292dc@gmail.com"},"message":"Avoid producing invalid string literals in #pragma expand output.\n\nPreviously, the characters \", /, and ? within string literals were not escaped in #pragma expand output, which could result in them being erroneously interpreted as ending the string literal, starting an escape sequence, or being part of a trigraph (respectively). Also, escape sequences were output in hexadecimal format. Since there is no length limit on hexadecimal escape sequences, this could result in subsequent characters in the string being interpreted as part of the escape sequence.\n\nThis fixes the issues by escaping the characters \", /, and ?, and by using three-digit octal escape sequences rather than hexadecimal ones.","distinct":true,"url":"https://api.github.com/repos/byteworksinc/ORCA-C/commits/9ff3407c60d9b3c57c2f49eb8c05d192fb64df56"},{"sha":"69f086367cc7c33489447c54fc8d5506da958972","author":{"name":"Stephen Heumann","email":"accfa2c3d6747a9e483bf951795ebb81992292dc@gmail.com"},"message":"Adjust how messages from the printf/scanf format checker are displayed.\n\nMainly, this causes the messages from the format checker to be displayed after the relevant line is printed, along with any other error messages. The wording and formatting of some of the messages is also slightly adjusted, but there should be no substantive change in what is warned about.","distinct":true,"url":"https://api.github.com/repos/byteworksinc/ORCA-C/commits/69f086367cc7c33489447c54fc8d5506da958972"},{"sha":"94ec3c73c7ad392f9a50c03559ed063ebbc8dde7","author":{"name":"Stephen Heumann","email":"accfa2c3d6747a9e483bf951795ebb81992292dc@gmail.com"},"message":"Various tweaks to printf/scanf format checking.\n\nIt is now stricter about invalid length modifiers. Also, \"comp\" is accepted where a floating-point type is expected (like the others, it is promoted to extended), and size specifiers are allowed with %n (now pretty much supported in the latest library version).","distinct":true,"url":"https://api.github.com/repos/byteworksinc/ORCA-C/commits/94ec3c73c7ad392f9a50c03559ed063ebbc8dde7"},{"sha":"ecff1e3479326dcf5de8728b1b2f599fb490df64","author":{"name":"Stephen Heumann","email":"accfa2c3d6747a9e483bf951795ebb81992292dc@gmail.com"},"message":"Don't give an error when format string is not a string literal.\n\nThis may be indicative of dubious code in some cases, but it can also have valid use cases that are not easy to modify.\n\nIf desired, this could be re-enabled under a separate lint flag (analogous to -Wformat-nonliteral in GCC/Clang, which is available as an option but is not included in -Wformat or -Wall).","distinct":true,"url":"https://api.github.com/repos/byteworksinc/ORCA-C/commits/ecff1e3479326dcf5de8728b1b2f599fb490df64"},{"sha":"7493ffa76c94d5d5eaa238c0cd2fd5171ccfa53b","author":{"name":"Stephen Heumann","email":"accfa2c3d6747a9e483bf951795ebb81992292dc@gmail.com"},"message":"Support the pause-on-errors feature for format checker messages.","distinct":true,"url":"https://api.github.com/repos/byteworksinc/ORCA-C/commits/7493ffa76c94d5d5eaa238c0cd2fd5171ccfa53b"},{"sha":"d3aff49550d688220402d1c70990cb647be7837c","author":{"name":"Stephen Heumann","email":"accfa2c3d6747a9e483bf951795ebb81992292dc@gmail.com"},"message":"Use escape sequences in format strings printed by the format checker.\n\nError messages are now lined up to account for the actual printed length of any escape sequences.","distinct":true,"url":"https://api.github.com/repos/byteworksinc/ORCA-C/commits/d3aff49550d688220402d1c70990cb647be7837c"},{"sha":"55dbc718c124c9289bdb49ab6e3e167d9ee3f5df","author":{"name":"Stephen Heumann","email":"accfa2c3d6747a9e483bf951795ebb81992292dc@gmail.com"},"message":"Small format checker adjustments.\n\nFormat checking for \"%p\" is improved: in the case of scanf, the corresponding argument must be a pointer to a pointer.","distinct":true,"url":"https://api.github.com/repos/byteworksinc/ORCA-C/commits/55dbc718c124c9289bdb49ab6e3e167d9ee3f5df"},{"sha":"0e341e11539f5892dad714f126f4ebbbcdce91dc","author":{"name":"Stephen Heumann","email":"accfa2c3d6747a9e483bf951795ebb81992292dc@gmail.com"},"message":"Record line numbers for certain auto variable declarations with initializers.\n\nThis allows debuggers to stop on the declaration lines, and also provides trace-back information for them if that feature is enabled.\n\nCurrently, this applies only to declarations that occur after the first statement in the block. As such, it doesn't change the handling of traditional pre-C99-style declarations at the beginning of a block.","distinct":true,"url":"https://api.github.com/repos/byteworksinc/ORCA-C/commits/0e341e11539f5892dad714f126f4ebbbcdce91dc"},{"sha":"cb0497687e9ed8431d0b90b0ae1acbc8dfdf655f","author":{"name":"Stephen Heumann","email":"accfa2c3d6747a9e483bf951795ebb81992292dc@gmail.com"},"message":"Update documentation to cover format checking and other recent changes.","distinct":true,"url":"https://api.github.com/repos/byteworksinc/ORCA-C/commits/cb0497687e9ed8431d0b90b0ae1acbc8dfdf655f"}]}
{"actor":{"display_login":"sheumann"}}