Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 741
    • Issues 741
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 197
    • Merge requests 197
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #17897
Closed
Open
Created May 13, 2020 by David Gobbi@dgobbiDeveloper

Allow compiler-specific preprocessor operators in wrapped headers

The wrappers can handle a broad variety of compiler-specific predefined macros, but they can't handle predefined operators like the following:

// gcc and clang
#if __has_attribute(x)
#if __has_cpp_attribute(x)
#if __has_builtin(x)
#if __has_include(x)
// clang
#if __has_include_next(x)
#if __has_feature(x)
#if __has_extension(x)
#if __has_warning(x)
#if __has_c_attribute(x)
#if __has_declspec_attribute(x)
#if __is_identifier(x)

The wrappers can implement some of these (like __has_feature() and __has_attribute()) to simply return zero. Others like __has_include() and __is_identifier() are trickier and should probably be left unimplemented.

Edited May 13, 2020 by David Gobbi
Assignee
Assign to
Time tracking