Hirohito Higashi wrote:
> Title is as it is.
> - Compiler optimizations will be a bit smarter.
> - Execution speed will be a bit faster.
> - Compiler us warn the code assignment wrong.
> - None. (maybe)
> I made a patch for proposal.
> How about this?
> When it's Okay, I'll continue with the remaining of the work.
In my experience using "const" does not really bring an advantage.
Changing the variable anyway would already cause a problem.
There is some inconvenience when a called function doesn't have "const",
it usually causes a ripple effect of changes. I can't remember a
mistake where using "const" would have avoided the problem.
GALAHAD: No, please. Please! I can defeat them! There's only a hundred.
GIRLS: He will beat us easily. We haven't a chance.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.