I'm working with a system that uses special macros a lot. For instance: class UDSSLib : public UFunctionLibrary { GENERATED_BODY() void foo(); int i; }

The problem is the GENERATED_BODY() line. It's not supposed to have a semicolon after it (I guess the macro expansion has that) and I'd like to stick to that style, but as is, everything after it gets indented too far -- as statement-cont syntax rather than statement. Can I either convince the C syntax analyzer that the specific string GENERATED_BODY() is a complete statement, or else cause the line after it to be indented normally?

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.