Skip to content

Wrong expansion order with nested macros #3442

Description

@slapin

When trying ifdefs in shaders found that these do not work, so the examples for preprocessor use are incorrect.
I found that if preprocessor_defines FOO`` used, one have to use #if FOOnot#ifdef FOO``` or else
syntax errors are reported.

line 1: Expecting a macro name after #ifdef, got: `1'

Metadata

Metadata

Assignees

No one assigned

    Labels

    Known Issueseasy workaround exists or too intrusive to fix right awaypriority: low

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions