On 6/23/08, Barry Smith <bsmith at mcs.anl.gov> wrote: > > A while ago I made XXType (MatType, VecType etc) const char* >
Well, you actually did #define VecType const char* instead of typedef const char* VecType; which IMHO is the right way. > I now think that was a mistake. Yep, the '#define' way can cause problems ;-) > I'd like to change them to just char* But why not the 'typedef' way ?? > Can anyone suggest a technical reason why this is a bad idea before I push > the code? > > Note this means if you have code like > > VecType t = VECMPI; > > you would need to change it to > > const VecType t = VECMPI; > Mmm, just a bit ugly you have to add the 'const' keyword. I insist: What would be the problem with ... ?? typedef const char* VecType; -- Lisandro Dalc?n --------------- Centro Internacional de M?todos Computacionales en Ingenier?a (CIMEC) Instituto de Desarrollo Tecnol?gico para la Industria Qu?mica (INTEC) Consejo Nacional de Investigaciones Cient?ficas y T?cnicas (CONICET) PTLC - G?emes 3450, (3000) Santa Fe, Argentina Tel/Fax: +54-(0)342-451.1594
