Message189130
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 |
|
Date |
User |
Action |
Args |
2013-05-13 13:39:19 | eli.bendersky | set | recipients:
+ eli.bendersky, amaury.forgeotdarc, belopolsky, gustavo, dgreiman, ext- |
2013-05-13 13:39:18 | eli.bendersky | set | messageid: <1368452358.92.0.988940188986.issue1772673@psf.upfronthosting.co.za> |
2013-05-13 13:39:18 | eli.bendersky | link | issue1772673 messages |
2013-05-13 13:39:18 | eli.bendersky | create | |
|