Author Topic: No semicolon after closing TEST_CLASS  (Read 338 times)

patrickkox

  • Community Member
  • Posts: 34
  • Hero Points: 1
No semicolon after closing TEST_CLASS
« on: January 11, 2020, 05:53:26 pm »
I don't know if this is a bug or just left-out since it applies to Visual Studio, but I noticed than when I enter the example code in Professional C++ (4th edition) There is no semicolon added after typing the open curly braces for the class.
So basically a "normal" class works fine, but when I type a TEST_CLASS for visual studio I get this:
Code: [Select]
#pragma once
#include <CppUnitTest.h>

TEST_CLASS(ObjectPoolTest)
{
}
This is on Debian 10 with SlickEdit 24.0.1.0 but also appears on the Raspberry Pi version (I didn't test this on a mac or Windows system).
« Last Edit: January 12, 2020, 04:37:04 pm by patrickkox »

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5253
  • Hero Points: 432
Re: No semicolon after closing TEST_CLASS
« Reply #1 on: January 12, 2020, 12:21:56 pm »
SlickEdit doesn't recognize that class definition. Looks like you have some preprocessing going on there. The SlickEdit tagging parser can be configured with some global preprocessing. The smart editing code doesn't support applying any preprocessing.

patrickkox

  • Community Member
  • Posts: 34
  • Hero Points: 1
Re: No semicolon after closing TEST_CLASS
« Reply #2 on: January 12, 2020, 04:41:33 pm »
As I understand this is required if you want to use the "Microsoft Visual C++ Testing Framework" so I don't think this applies to SlickEdit. I don't use the Microsoft tools, so this doesn't apply to my situation. I just noticed this when doing some of the examples in my C++ book. But maybe other people like to develop on SlickEdit but want to use the Visual C++ Testing framework?

dunkers

  • Senior Community Member
  • Posts: 693
  • Hero Points: 28
Re: No semicolon after closing TEST_CLASS
« Reply #3 on: January 13, 2020, 06:54:34 pm »
I think it's a cpputest thing rather than Visual C++ thing - I see the same using cpputest and I don't have any Microsoft development tool at all.