Hi, We have recently upgraded our unit test suite from Boost 1.35.0 to 1.42.0. Now we have the following problem: Some of our unit test applications take command-line parameters of their own, and there seem to be name conflicts with command-line options of Boost.Test. For example, some of our test applications accept a command line parameter "-f", which takes no arguments. However, Boost.Test also accepts a "-f" parameter, which takes 1 argument. So whenever we specify our "-f" option when running a test, we get an error message from Boost.Test similar to the following: "Invalid output format: -L" We don't like the idea of changing our own command-line interface, because some tests take a lot of command-line parameters with short names, and there are likely to be new name conflicts with future Boost versions. Is there an easy way to disable or bypass the command-line parser of Boost.Test, or at least to disable parsing of short options? -- Florian Winter Senior Software developer Motama GmbH Lortzingstraße 10 · 66111 Saarbrücken · Germany tel +49 681 940 85 50 · fax +49 681 940 85 49 mlohse@motama.com · www.motama.com Companies register · district council Saarbrücken · HRB 15249 Law registered office · Saarbrücken CEOs · Dr.-Ing. Marco Lohse, Michael Repplinger This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.