quote:

---

Originally posted by WannabeeDeveloper
...and as soon as you remove this "special" character, everything works okay?

---

quote:

---

Originally posted by WannabeeDeveloper
If so, can you provide a small solution/project which shows this behaviour for us to download, so we can reproduce the problem and fix it?

---

class Test
{
	void Method1() // Parsed OK
	{

	}

	void Method2() // Parsed incompletely ?
	{
		// Here will go special character: ++ (win-1251 codepage)
	}

	void Method3() // Not parsed!
	{
	}
};

quote:

---

Originally posted by thims

Sure. Here is 0xFE.cpp source:

class Test
{
	void Method1() // Parsed OK
	{

	}

	void Method2() // Parsed incompletely ?
	{
		// Here will go special character: ++ (win-1251 codepage)
	}

	void Method3() // Not parsed!
	{
	}
};

Just open it with VS.NET 2003 with VAX 10.1 installed and try to list methods in the VAX's dropdown.

---

quote:

---

Originally posted by axel014

i have encountered a somewhat similar problem, but using a plain english comment; here is a little example:

typedef struct
{
int x;
} /*comment*/ Foo;

Foo x;
x.

as long as the /*comment*/ is there, x. will not pop up the members list or make any autocomplete suggestion.. it's not really usual to place comments in that spot, but somehow i did it :)

i'm using VAX 10.1.1293.0..

---

quote:

---

Originally posted by WannabeeDeveloper

Definitely a Bug.
case=500

---

quote:

---

Originally posted by thims

I hope, Whole Tomato will fix it in the nearest time. For now I cannot use it at all: my codebase contains too many these characters. :(

---