Boost C++ Libraries: Ticket #220: Inconvinient macro name 'i' makes VisualAssist to confuse

david_abrahams — Mon, 15 Dec 2003 17:38:34 GMT

Logged In: YES
user_id=52572
There's not much we can do about VisualAssist.  This is their
bug, since "i" is subsequently un-defined a few lines later.

kodt — Tue, 16 Dec 2003 08:53:14 GMT

Logged In: YES
user_id=890789
Well, if it's a problem of VisualAssist (in fact, it's a problem of
an end user), there is another inconvinience.
If one writes some code as follows:
#include <complex>
#define i std::complex<double>(0.0,1.0)
#include <boost/type_traits.hpp>
// here i is undefined
#include <iostream>
main()
{
  std::cout << i*i << std::endl; // expect -1
}
I believe, boost should be more careful with commonly used
identifiers.

pavel_kuznetsov — Tue, 16 Dec 2003 09:04:25 GMT

Logged In: YES
user_id=230164
That's right, it's a bug in Visual Assist. On the other hand it
should not take too many efforts to help VA changing the name
of the variable in question to something considerably less
frequently used.

status changed

John Maddock — Wed, 16 Mar 2005 17:12:06 GMT

status assigned → closed

Logged In: YES
user_id=14804
I've just committed some patches to cvs that fix this, "i"
is no longer used as a macro name inside the type_traits lib.
John Maddock.