Where to place tests for BOOST_WORKAROUND?

Hi guys, despite proceeding on it by fits and starts I've completed the work on the new compiler identification macros. Since Rene asked for them to be committed after the 1.34 release they are still on hold (/auto-censorship here/) however I'd like to add tests for the new BOOST_WORKAROUND macro. The question is: it was, and is, a sort of private tool for boost developers, as its placement in the detail/ subdirectory emphasizes, so we probably (uncertainty and doubt) don't want its test results to show in the regression reports. If so, where should those tests go? -- [ Gennaro Prota, C++ developer for hire ]

Gennaro Prota wrote:
despite proceeding on it by fits and starts I've completed the work on the new compiler identification macros. Since Rene asked for them to be committed after the 1.34 release they are still on hold (/auto-censorship here/) however I'd like to add tests for the new BOOST_WORKAROUND macro. The question is: it was, and is, a sort of private tool for boost developers, as its placement in the detail/ subdirectory emphasizes, so we probably (uncertainty and doubt) don't want its test results to show in the regression reports. If so, where should those tests go?
I don't know, but we should have some - possibly minimal - docs for this new BOOST_WORKAROUND too. You're welcome to put everything under libs/config, but I've no idea if that's the best place. John.

On Tue, 1 Aug 2006 09:56:08 +0100, "John Maddock" <john@johnmaddock.co.uk> wrote:
I don't know, but we should have some - possibly minimal - docs for this new BOOST_WORKAROUND too.
Sure. The old version had an explanation directly in its source file. If there are no objections I'll do the same for the new one.
You're welcome to put everything under libs/config, but I've no idea if that's the best place.
You know, I ask just because CVS makes it annoying to move files around, at least when they have a significant edit history. Thanks for the directory hospitality :-) -- [ Gennaro Prota, C++ developer for hire ]
participants (2)
-
Gennaro Prota
-
John Maddock