Bug #28898

Rapify files with PreProcessor (with macro) generate Lint error

Added by test over 3 years ago. Updated over 3 years ago.

Status:Rejected Start date:02/23/2012
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Affected Version:

Description

Example:

I try create PBO with rapify of description.ext, that have macro.

Example class in my description.ext:

#define GVAR(var) lo_##var
class Params {
    class GVAR(MyVarWithPre) { -this line will generate Lint Error (type: Expected class name)
        title = "aaaaaa";
        values[] = {1,2,3};
        default = 1;
        texts[] = {"lo","lo","lo"};
    };
};

History

Updated by test over 3 years ago

  • Description updated (diff)

Updated by mikero over 3 years ago

  • Status changed from New to In progress

Updated by mikero over 3 years ago

  • Status changed from In progress to Rejected

above syntax is absolutely standard fare. there are no rapify errors or lintchecks with above

must be a typo elsewhere in the code and rapify at-the-least will give you a line# where it's disgusted with something

tested on last 3 series of dll releases. all=ok

Updated by mikero over 3 years ago

description.ext CANNOT be binarised (rapified) it can be Lintchecked.

when making a pbo via MakePbo.exe this is automitally done.

there is btw, no reason to prebinarise any file prior to using MakePbo. All is taken care of, automatically.

Also available in: Atom PDF