Whole Tomato Software Forums

Whole Tomato Software Forums

All Forums

Visual Assist

You must be registered to post a reply.
Click here to register.

Screensize:

UserName:

Password:

Format:

Message:

Forum code is on.
Html is off.

Check to include your profile signature.
Check to subscribe to this topic.

T O P I C R E V I E W
.oisyn	Posted - Nov 02 2008 : 6:19:36 PM When using VC++'s __restrict extension, VA X shows __restrict with a red error underline. void Foo(void * __restrict a, void * __restrict b) { } Note that __restrict is part of the ISO C99 standard, but that microsoft supports it in C++ as well. It would be nice if VA X did that too.
4 L A T E S T R E P L I E S (Newest First)
feline	Posted - Dec 20 2010 : 2:58:50 PM Can you try the following please. Edit VA's "StdAfx.h" file as explained in this FAQ entry: http://docs.wholetomato.com?W302 and add the entry: #define restrict __restrict at the bottom. This file is used to help VA's parser with difficult code, and can be used to work around odd effects. After modifying this file you need to rebuild the VA symbol database for the changes to take effect: VA Options -> Performance -> General -> Rebuild symbol databases I have just tried this here, and based on a few simple tests it seems to be working well.
zeroes00	Posted - Dec 17 2010 : 4:01:39 PM The new Intel c++ compiler supports restrict keyword (without the underscore prefixes) but VA X doesn't recognize that. To my understanding it's the same thing as the underscored VC++ extension and I'd like to use it because it's shorter to write.
support	Posted - Dec 01 2008 : 07:45:58 AM case=20732 is fixed in build 1707
accord	Posted - Nov 04 2008 : 2:46:53 PM I am seeing the same effect here. Thank you for the clear description. case=20732