#9734: Provide macro __GLASGOW_HASKELL_TH__ -------------------------------------+------------------------------------- Reporter: nomeata | Owner: Type: feature | Status: new request | Milestone: 7.10.1 Priority: normal | Version: 7.8.3 Component: Compiler | Keywords: Resolution: | Architecture: Unknown/Multiple Operating System: | Difficulty: Unknown Unknown/Multiple | Blocked By: Type of failure: | Related Tickets: None/Unknown | Test Case: | Blocking: | Differential Revisions: | -------------------------------------+------------------------------------- Description changed by nomeata: Old description:

The Debian packaging added a few hacks to create a CPP macro that can be used to distinguish compilers with Template Haskell support from those that don’t have that support. We need this to compiler some code on non- TH architectures.

It works, but we found that we cannot upstream such patches, which is a shame.

I propose that among the GHC-defined macros listed at https://www.haskell.org/ghc/docs/latest/html/users_guide/options- phases.html#c-pre-processor there is also `__GLASGOW_HASKELL_TH__=YES`, which is available if the compiler supports splices, or ``__GLASGOW_HASKELL_TH__=NO` if not.

(I propose a two-valued comparison so that library authors can decide themselves what the default should be if this symbol is not defined, some might want to use TH on older compilers, some not.)

I hope this can be part of 7.10.

New description: The Debian packaging added a few hacks to create a CPP macro that can be used to distinguish compilers with Template Haskell support from those that don’t have that support. We need this to compiler some code on non- TH architectures. It works, but we found that we cannot upstream such patches, which is a shame. I propose that among the GHC-defined macros listed at https://www.haskell.org/ghc/docs/latest/html/users_guide/options- phases.html#c-pre-processor there is also `__GLASGOW_HASKELL_TH__=YES`, which is available if the compiler supports splices, or `__GLASGOW_HASKELL_TH__=NO` if not. (I propose a two-valued comparison so that library authors can decide themselves what the default should be if this symbol is not defined, some might want to use TH on older compilers, some not.) I hope this can be part of 7.10. -- -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/9734#comment:1> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

#9734: Provide macro __GLASGOW_HASKELL_TH__ -------------------------------------+------------------------------------- Reporter: nomeata | Owner: Type: feature | Status: patch request | Milestone: 7.10.1 Priority: normal | Version: 7.8.3 Component: Compiler | Keywords: Resolution: | Architecture: Unknown/Multiple Operating System: | Difficulty: Unknown Unknown/Multiple | Blocked By: Type of failure: | Related Tickets: None/Unknown | Test Case: | Blocking: | Differential Revisions: Phab:D386 | -------------------------------------+------------------------------------- Comment (by Austin Seipp <austin@…>): In [changeset:"c211f8e55b8dd1d43854ce3c4554ffbafb0009f9/ghc"]: {{{ #!CommitTicketReference repository="ghc" revision="c211f8e55b8dd1d43854ce3c4554ffbafb0009f9" Add __GLASGOW_HASKELL_TH__=YES/NO to CPP definitions Test Plan: None really. Reviewers: austin Reviewed By: austin Subscribers: thomie, carter, simonmar Differential Revision: https://phabricator.haskell.org/D386 GHC Trac Issues: #9734 }}} -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/9734#comment:3> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

#9734: Provide macro __GLASGOW_HASKELL_TH__ -------------------------------------+------------------------------------- Reporter: nomeata | Owner: Type: feature request | Status: closed Priority: normal | Milestone: 7.10.1 Component: Compiler | Version: 7.8.3 Resolution: fixed | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: #11322 | Differential Rev(s): Phab:D386 Wiki Page: | -------------------------------------+------------------------------------- Changes (by hvr): * related: => #11322 Comment: Turns out, using `YES`/`NO` as values for CPP constants is not a good idea... :-/ -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/9734#comment:5> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler