Update 2024-03-21-setjmp-plus-longjmp-equals-goto-but-awesome.md

MyNameIsTrez · web-flow · commit 0519b45459c7 · 2024-12-26T13:54:35.000+01:00
diff --git a/_posts/2024-03-21-setjmp-plus-longjmp-equals-goto-but-awesome.md b/_posts/2024-03-21-setjmp-plus-longjmp-equals-goto-but-awesome.md
@@ -77,9 +77,9 @@ bool foo(int *result) {
 }
 ```
 
-Adding this attribute to every function, and requiring the output of any function to go through an output parameter, is quite ugly though.
+Adding this attribute to every function, and requiring the output of any function to go through a result parameter, is quite ugly though.
 
-It's possible to have the result be returned, and the bool be filled through an output parameter, but then `__attribute__((warn_unused_result))` can't verify if the function's status is used.
+It's possible to swap the bool and the result, by having the result be returned, and the bool be filled through a parameter, but then `__attribute__((warn_unused_result))` isn't verifying that the function's status is used.
 
 # goto?
 

Original file line number	Diff line number	Diff line change
`@@ -77,9 +77,9 @@ bool foo(int *result) {`
`77`	`77`	`}`
`78`	`78`	```
`79`	`79`
`80`		`-Adding this attribute to every function, and requiring the output of any function to go through an output parameter, is quite ugly though.`
	`80`	`+Adding this attribute to every function, and requiring the output of any function to go through a result parameter, is quite ugly though.`
`81`	`81`
`82`		-It's possible to have the result be returned, and the bool be filled through an output parameter, but then `__attribute__((warn_unused_result))` can't verify if the function's status is used.
	`82`	+It's possible to swap the bool and the result, by having the result be returned, and the bool be filled through a parameter, but then `__attribute__((warn_unused_result))` isn't verifying that the function's status is used.
`83`	`83`
`84`	`84`	`# goto?`
`85`	`85`