Prev: Project to recover UnderC C/C++ interpreter
Next: An Algorithm Intensive Programming Contest - Manthan @ Codefest - IT-BHU
From: Daniel T. on 26 Mar 2010 05:43 Nick Hounsome <nick.hounsome(a)googlemail.com> wrote: > > I attribute my mistake to the fact that being in the "no const" camp I > only ever use const for reference and pointer parameters where it DOES > make a difference. So being in the "no const" camp means to use const everywhere it is useful but not where it isn't? How is that no const? I thought someone was only in the "no const" camp if they only used const where the compiler forced them to... -- [ See http://www.gotw.ca/resources/clcm.htm for info about ] [ comp.lang.c++.moderated. First time posters: Do this! ] |