I don't care much about the guard name, so if Qt Creator had a way to fix that in the header I would be happy with whatever format Qt used. It is fine to leave the renaming of files and the changing of guard names and #include references as an option that can be turned off for those people who like to do more work manually. But it is an essential option. Anything that can be automated, should be.
John On Feb 4, 2010, at 3:40 AM, Danny Price wrote: > > > On Thu, Feb 4, 2010 at 12:49 PM, Gena Cid <gena...@inbox.ru> wrote: > This is too strong! And too complex: think, for example, about doxygen > comments. And about guard' names (I mean #ifndef-#define-#endif). And cmake- > or Makefile-based projects? > > I would say that guard names and comments are up to the user to fix. That's > trivial next to the hoops you currently have to jump through to refactor > files in Creator. > > > > If this feature be in QtC sometime, it must be an option! > > -----|- > Gena. > _______________________________________________ > Qt-creator mailing list > Qt-creator@trolltech.com > http://lists.trolltech.com/mailman/listinfo/qt-creator > > _______________________________________________ > Qt-creator mailing list > Qt-creator@trolltech.com > http://lists.trolltech.com/mailman/listinfo/qt-creator
_______________________________________________ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
