3 ms·
> The nice part about it is that you can use a consitent naming convention even when using external libraries. I think a slightly nicer (in the sense that it w
by wtetzner 12y ago
> The nice part about it is that you can use a consitent naming convention even when using external libraries.
I think a slightly nicer (in the sense that it would catch more typos) way to do it might be to specify the naming convention at the top of the source file, and have the compiler enforce that naming convention within the file.
Maybe also have a way to set it in the build system, so it could enforce it for the whole project. That way your project is consistent, but the libraries you rely on don't have to match your conventions.
- Retra 12y agoI was about to say the same thing (about enforcing the convention directly.) But there's a problem. Let's say I write a function called `HTTPHeaderScan()`. Someone else might have used `HttpHeaderScan()`. Or worse: `HtTpHeAdErScAn()`. How do you enforce one over the other? If you said "everthing must be CamelCase," how do you know that the name is wrong?
- rat87 12y agoAssuming you have a consistent naming scheme for your language I'd assume this would be mostly used to call libraries written in other languages