In the C code I'm currently working with `return(false)` usually means "error" but sometimes it just means "false". Claude's take: "The dual-meaning of `return(false)` is a deep C-era pattern not worth unraveling." It's not wrong, but still troubling.