Ok then on the apology, thank you.
<--- I still think that thing looks silly, but whatever. Anyhow, ANSI C isn't something hypothetical, it's what all workable compilers are based upon. If GCC optimizes const away then that's cool, but I'm sure it would afford the same luxury to the repetitive occurrences of constant type values that were stuffed in by the preprocessor thru the use of #define. I can see the benefit of securing the type, especially in the minds of native C++ coders that tend to worry about such things. But I also appreciate the efficiency of letting the compiler pick the type on an as needed basis.
This brings us to the OP's original question. I think the answer is more a matter of monkey see monkey do with the int LEDPin thing. It's certainly not the most efficient way and it's even the wrong basic type to supply as arguments to the functions. But, it is what you will see throughout the examples.
I thought it was simple enough, I just wanted to know why the local allegiance to const over #define. It seemed to be perfectly appropriate to the course of the conversation at that point. At least I thought so.
The "bring it on" thing is about debate, not a duel. I like to argue about technical matters, it's how I learn. I am also willing to admit I'm wrong when there is a technical backing to the counter-claim. I'm not a big fan of "because I said so", or "that's the way it is here" etc. I like to see real proof and hear real logical reasoning behind an argument. When I post, I expect to be questioned if I make a technical error. I don't expect to be admonished for something I didn't do.
I apologize to the OP for this diversion. I like to try and help, but sometimes I guess I rub some folks the wrong way.