| T O P I C R E V I E W |
| bugfix |
Posted - Jul 03 2006 : 1:04:03 PM
huh?
-bugfix |
| 7 L A T E S T R E P L I E S (Newest First) |
| bugfix |
Posted - Jul 20 2006 : 05:11:58 AM
quote:
Originally posted by feline
maybe, but as someone who spends quite a lot of time reproducing bugs in VA i can assure you 1301 had its share of problems :)
i still remember the regular posts about poor template support from the parser.
From my expierince 1301 does a much better job when it comes to templates and smartptr and I use those extensively.
quote:
still, to put things in perspective, try using a machine that does not have VA installed *shudder* now that is an unpleasant experience!
No I wont try:) |
| feline |
Posted - Jul 18 2006 : 7:33:05 PM
maybe, but as someone who spends quite a lot of time reproducing bugs in VA i can assure you 1301 had its share of problems :)
i still remember the regular posts about poor template support from the parser.
still, to put things in perspective, try using a machine that does not have VA installed *shudder* now that is an unpleasant experience! |
| bugfix |
Posted - Jul 18 2006 : 03:15:03 AM
vs2003 vax disabled:
vs2003 w/ my beloved vax build 1301:)
here vax colors name as variable b/c it finds: wxThemeInfo.name | wxString name
and args is colored b/c of: System.Runtime.Remoting.Messaging.MethodCall.args | System.Object[] args : System.Object[] args
but at least it's consistent! 1301 parser still outperforms any later builds for c++.
|
| jpizzi |
Posted - Jul 18 2006 : 01:14:20 AM
If you disable VA, you get
Still weird, even without VA (notice the first "#" in the stringify operator). |
| bugfix |
Posted - Jul 04 2006 : 11:39:21 AM
Ok.. not using macros that much I prefer templates when possible:)
Anyways, why is name colored twice as variable and one time as type?
|
| support |
Posted - Jul 03 2006 : 6:40:26 PM
mmb's observation is correct.
VA X makes some reasonable guesses while coloring preprocessor macros. The only other option is to not color them at all. |
| mmb |
Posted - Jul 03 2006 : 4:39:21 PM
Was it ever different? We have a lot of more or less complicated macros in our project and most of them looks this way.
I would guess that if the macro parameter is a name of a local/global variable somewhere it is bold/normal or otherwise even "not enhanced" like args.
Happens in both VC6 and VC2005. |
