Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
P
prime
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 129
    • Issues 129
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Haskell
  • prime
  • Wiki
  • language pragma

Last edited by ravi@bluespec.com Nov 21, 2009
Page history New page

language pragma

Proposal: LanguagePragma

Ticket #128
Dependencies none
Related specific item in NewPragmas

Compiler support

GHC full
nhc98 none
Hugs none
UHC none
JHC none
LHC full

Summary

Document the minimum guarantees provided by the LANGUAGE pragma.

Description

GHC and Cabal (via Language.Haskell.Extension) have been successfully using the LANGUAGE pragma for the following two purposes:

  1. Document the post-Haskell98 language extensions a source file requires.

  2. Locally enable those required language extensions when compiling an extension-using source file.

The goal of this proposal is to specify the minimum guarantees provided LANGUAGE pragma so that it can be used portably for those same purposes across Haskell 2010 implementations.

References

  • Compiler Pragmas in Haskell 98

  • Pragmas in the GHC User's Guide

  • Language.Haskell.Extension - a data type representing Haskell language extensions (as understood by Cabal).

  • Scheme Requests for Implementation - "A forum for people interested in coordinating libraries and other additions to the Scheme language between implementations"

  • SRFI 0: Feature-based conditional expansion construct - A baseline mechanism for Scheme users to check the availability of and manage access to specific SRFIs

Report Delta

Replace the the following sentence in http://www.haskell.org/onlinereport/pragmas.html 11 Compiler Pragmas:

An implementation is not required to respect any pragma, but the pragma should be ignored if an implementation is not prepared to handle it.

with

An implementation is not required to respect any pragma and any pragma can be ignored if an implementation is not prepared to handle it. However, implementations are strongly encouraged to support the LANGUAGE pragma described below as there are many language extensions being used in practice.

Add the following subsection

11.3 Language Extensions

The LANGUAGE pragma is a file-header pragma. A file-header pragma must precede the module keyword in a source file. There can be as many file-header pragmas as you please, and they can be preceded or followed by comments. An individual language pragma begins with the keyword LANGUAGE and is followed by a comma-separated list of named language extensions.

For example, to enable the FFI and preprocessing with CPP:

{-# LANGUAGE ForeignFunctionInterface, CPP #-}

If a Haskell implementation does not recognize or support a particular language extension that a source file requests (or cannot support the combination of language extensions requested), any attempt to compile or otherwise use that file with that Haskell implementation must fail with an error.

In the interests of portability, multiple attempts to enable the same, supported language features (e.g. via command-line arguments, implementation-specific extension dependencies or non-standard pragmas) are specifically permitted. Haskell 2010 implementations that support the LANGUAGE pragma are required to support {-# LANGUAGE Haskell2010 -#}. Those implementations are also encouraged to support the following named language extensions: DoAndIfThenElse, HierarchicalModules, FixityResolution, PatternGuards, NoNPlusKPatterns, RelaxedDependencyAnalysis, LineCommentSyntax, EmptyDataDeclarations, LanguagePragma and ForeignFunctionInterface. These are the named language extensions, supported by some pre-Haskell 2010 implementations, that have been integrated into this report.

Clone repository Edit sidebar
Wiki

Title Index