Wouldn't it be better to only enable Haskell2010 and XmlSyntax and then
rely on LANGUAGE pragmas? I guess optimally we want to add support for
-Xoptions to
hsx2hs but in the mean time…
BTW I think hsx2hs is in fact affected by these backwards-incompatible
changes, and lacks an upper bound on its H
> The first primary reason is
> technical: haskell-src-exts
> 1.14 revamps the Extension
> datatype, among other things
> to allow turning extensions on
> and off (similar to what Cabal
> allows). We also introduce the
> concept of a Language,
> separate from a set of
> extensions. This is the only
HSE parses based on pragmas by default. This can be configured through the
ParseMode [1].
But your question regards HSP, Haskell Server Pages, which indeed just
enables most extensions by default. Right now there's no way to configure
that, but it shouldn't be hard for a skilled programmer to fix.
Well if you enable TemplateHaskell then code like foo$bar gets a new
meaning and if you enable Arrows then proc is a reserved keyword, etc etc.
On Tue, Aug 20, 2013 at 1:06 PM, Mateusz Kowalczyk
wrote:
> On 20/08/13 11:56, Dag Odenhall wrote:
> > Good stuff!
> >
> > Is there any way, or plans fo
On 20/08/13 11:56, Dag Odenhall wrote:
> Good stuff!
>
> Is there any way, or plans for a way, to parse a file based on its LANGUAGE
> pragmas? Last I checked e.g. HSP simply enabled all extensions when
> parsing, which can cause code to be parsed incorrectly in some cases.
>
>
Can you give any
Good stuff!
Is there any way, or plans for a way, to parse a file based on its LANGUAGE
pragmas? Last I checked e.g. HSP simply enabled all extensions when
parsing, which can cause code to be parsed incorrectly in some cases.
On Tue, Aug 20, 2013 at 10:15 AM, Niklas Broberg
wrote:
> Fellow Hask
