Message189130
| Author |
eli.bendersky |
| Recipients |
amaury.forgeotdarc, belopolsky, dgreiman, eli.bendersky, ext-, gustavo |
| Date |
2013年05月13日.13:39:18 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1368452358.92.0.988940188986.issue1772673@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
For external APIs visible to user code, this can cause some compatibility problems and users may need to at the very least re-compile this code. So -1 here.
For new external APIs, having const wherever appropriate should be considered on a case by case basis.
For internal code this is a good idea, but I wouldn't go mass-slashing all the code base now replacing char* by const char*. Presenting some examples where this makes sense in particular would be interesting though. +0 |
|