Markus Schöpflin wrote: > > Daniel Frey wrote: > > > Markus Schöpflin wrote: > > >>This was the original source: > >> > >>template<bool, typename> struct enable_if; > >>-----------------------^ > >> > >>Visual Age doesn't like this, it needs a name here. > > > > ^^^^^^^^^^ > > > > Ah, that's the reason. But given my recent discomfort about > > unmaintainable code, look at it again: > > > > # if BOOST_WORKAROUND(__HP_aCC, <= 33900) > > template<bool cond, typename T> struct enable_if; > > # else > > template<bool, typename T> struct enable_if; > > # endif > > > > Does this really makes sense? Shouldn't we just keep one version with > > names for template parameters? AFAICS this should work for all compilers > > and it could be a general boost coding guideline to always provide names > > for template parameters. Comments? > > Agreed, if it works for all compilers, let's just keep the version > with the names. (And add a comment that it should stay like it is!)
No, don't add a comment. Let's make it a boost coding guideline, otherwise we will clutter the code again with comments instead of workarounds. Remember that this is only one example of a line with template parameters. Would you like to add a comment for every line all over boost? Regards, Daniel -- Daniel Frey aixigo AG - financial training, research and technology Schloß-Rahe-Straße 15, 52072 Aachen, Germany fon: +49 (0)241 936737-42, fax: +49 (0)241 936737-99 eMail: [EMAIL PROTECTED], web: http://www.aixigo.de _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost