We are attempting to use Visual Assist X with our own include files. Each include file has a block of text at the top which is in the following format:
#ifdef HYPER
^Title^
%Description:%
Blah blah blah.
%Available Functions:%
~function_name~nnnn_nnnn_filename~ - This function does stuff
#endif
This block of text is completely throwing the parser in that the first structure defined in the header is not recognised. Is there a way to instruct the parser to skip a block in a header file?
We are going to get around the problem by enclosing the #ifdef HYPER block in a c style comment. But out of interest, would you expect visual assist x to handle blocks of text in header files?
As you have discovered, VA X assumes #ifdef/#endif surrounds code, not text. It does this for a number of reasons.
There is no clean way to get around the behavior. Adding comment blocks is certainly a great workaround, assuming you have permission to update all of your source files.
Topic Locked
Posted - Oct 14 2004 : 05:10:33 AM
