Boost logo

Ublas :

From: Nico Galoppo (nico_at_[hidden])
Date: 2007-04-07 11:33:35

Hi Joe,

I would be in favor of such a change. I think that the way you propose to do it
is transparent and compatible with previous 'default' behavior. The best way to
proceed is probably that you produce a patch against the current state of CVS
and pass it on to someone who has CVS write access.


Joe Gottman wrote:
> I recently ran some code in debug mode and was astonished at how
> long it took to run. After profiling I discovered that the bottleneck
> was caused by the uBlas debug macros. Since I still needed to debug the
> code but couldn't afford to spend 40 minutes on a single test run, I
> manually defined all the uBlas NDEBUG macros to disable the uBlas
> checking while still being able to use the debugger. This worked, but
> it was extremely inconvenient and time-consuming.
> It would be nice if you allowed users to define a BOOST_UBLAS_NDEBUG
> macro to disable only the uBlas debug macros. Then in
> boost/numeric/ublas/detail/config.hpp, you can replace the line
> #ifdef NDEBUG
> with
> #if defined(NDEBUG) || defined(BOOST_UBLAS_NDEBUG)
> and the user will be able to disable the uBlas check macros and still be
> able to debug.
> Joe Gottman

nico galoppo von borries     |  address: 119 fidelity st., carrboro
comp. graphics phd. student  |           north carolina, 27510 USA
UNC, chapel hill             |  phone: +1 (919) 962-1898 (office)
                              |         +1 (919) 942-4388 (home)
                              |  email: nico at cs dot unc dot edu
                              |  homepage: