Re: [Monotone-devel] Re: The new macro M is no good...

[Nathaniel Smith]

On Wed, Jul 27, 2005 at 08:28:28AM -0500, Brian Downing wrote:
> Traditionally Visual C++ (6 at least) has had __LINE__ not expand into a
> literal number when the "Fix and Continue" debugging option is on.  This
> is so all the __LINE__ references can be kept up to date as the code
> changes.  Yes, this quite possibly flies in the face of ANSI, but they
> do it anyway.  The only way to get around it is to turn that off, which
> also disables the cool incremental compilation while debugging.

Ugh.

Of course, we don't compile on VC++ at all ATM, so I'm not sure how
problematic this is :-).

> Couldn't you also make it:
>   Musing<typeof(cs)> this_is_a_musing_fnord_object_VARIABLENAME(cs, "cs", 
> __FILE__, __LINE__, __PRETTY_FUNCTION__)
> 
> and both be save vs. VC++ damage and multiple calls per line?

We thought of that, but it loses on things like M(*i).

-- Nathaniel

-- 
When the flush of a new-born sun fell first on Eden's green and gold,
Our father Adam sat under the Tree and scratched with a stick in the mould;
And the first rude sketch that the world had seen was joy to his mighty heart,
Till the Devil whispered behind the leaves, "It's pretty, but is it Art?"
  -- The Conundrum of the Workshops, Rudyard Kipling