• Arjan <arjan ask.me> Jul 07 2006
• "Pavel Vozenilek" <pavel_vozenilek yahoo.co.uk> Jul 07 2006
• Arjan <arjan ask.me> Jul 07 2006
• Arjan <arjan ask.me> Jul 07 2006
• Walter Bright <newshound digitalmars.com> Jul 07 2006
• "Pavel Vozenilek" <pavel_vozenilek yahoo.co.uk> Jul 09 2006
• Arjan <arjan ask.me> Jul 10 2006

8.49.2 vs 8.48.10

see http://www.digitalmars.com/~arjan/boost/status/dmc8492/cs-dmc.html

Arjan

"Arjan" wrote:

 8.49.2 vs 8.48.10

 see http://www.digitalmars.com/~arjan/boost/status/dmc8492/cs-dmc.html


That's /very/ useful tool.


I was told that Metacom had switched their tests
week ago but nothing is visible. I planned to set
something like this but didn't find enough of courage.

/Pavel

Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Pavel Vozenilek wrote:
 "Arjan" wrote:
 
 8.49.2 vs 8.48.10

 see http://www.digitalmars.com/~arjan/boost/status/dmc8492/cs-dmc.html


 That's /very/ useful tool.
 
 
 I was told that Metacom had switched their tests
 week ago but nothing is visible. I planned to set
 something like this but didn't find enough of courage.
 
 /Pavel
 
 


I know what you mean ;-) Took me quite some time before I had it going.

Attached a zip containing my modification to boost tools/build/v1/dmc-* 
and 2 command scripts.
Extract in boost root dir.
Run from the status dir dmcstatus.cmd. After a while a few crashed 
asserts etc there will new cs-win32-*.html files.

Arjan

Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

oops wrong attachement

Arjan wrote:
 8.49.2 vs 8.48.10
 
 see http://www.digitalmars.com/~arjan/boost/status/dmc8492/cs-dmc.html
 
 Arjan


This is great for checking the status.

It looks like the column labeled 8.48.10 should be 8.49.1 ? I didn't 
think 8.48.10 passed any of the type_traits tests.

"Arjan" wrote:

 8.49.2 vs 8.48.10

 see http://www.digitalmars.com/~arjan/boost/status/dmc8492/cs-dmc.html


It would be useful to define BOOST_STRICT_CONFIG
macro value, e.g. inside boost/detail/workaround.hpp.

That would get rid few DMC related workarounds
in Boost code. They may be obsolete currently
or may hide fixeable bugs.

/Pavel

Pavel Vozenilek wrote:
 "Arjan" wrote:
 
 8.49.2 vs 8.48.10

 see http://www.digitalmars.com/~arjan/boost/status/dmc8492/cs-dmc.html


 It would be useful to define BOOST_STRICT_CONFIG
 macro value, e.g. inside boost/detail/workaround.hpp.
 
 That would get rid few DMC related workarounds
 in Boost code. They may be obsolete currently
 or may hide fixeable bugs.
 
 /Pavel
 
 


Good tip!
Will rerun the regression test with -DBOOST_STRICT_CONFIG for both last 
beta and 8.48.

Arjan