Subject: Re: [boost] boost.foreach overhead
From: Kai Schroeder (kaischroeder3_at_[hidden])
Date: 2010-10-18 04:16:22
On Mon, Oct 18, 2010 at 5:03 AM, Vladimir Prus <vladimir_at_[hidden]>wrote:
> OvermindDL1 wrote:
> > On Sun, Oct 17, 2010 at 3:47 PM, Eric Niebler <eric_at_[hidden]> wrote:
> >> On 10/17/2010 2:39 PM, Christopher Jefferson wrote:
> >>> Having to step through 69 steps to go through
> >>> each stage of a for loop makes debugging almost impossible.
> >>> It is for precisely this reason that most projects I work on forbid
> >>> BOOST_FOREACH, and a similar preprocessing madness. They just make
> >>> debugging, and tracking down compile-time errors, too hard.
> >> What debugger do you use? Visual Studio doesn't give me this grief.
> > Ditto, but even if it did I could setup a debugging filter in it to
> > ignore the extra steps in the VS debugger, can you not do that in GDB?
> Suprise -- no, you cannot.
As GDB is completely scriptable you can of course do that
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk