FWIW, even the British can't entirely make up their mind about whether to -ize or to -ise:
http://blog.oxforddictionaries.com/2011/03/ize-or-ise/ The advantage of *not* introducing aliases is that it makes it that much easier to exhaustively test whether some extension is turned on - it means extensions have a canonical name that everyone uses. On 26 January 2015 at 17:42, Yitzchak Gale <[email protected]> wrote: > Even though my native English is the U.S. > variety, I still haven't gotten used to writing > > {-# LANGUAGE GeneralizedNewtypeDeriving #-} > > It's a constant compiler error for me. I'm just so accustomed > to the idea that in the Haskell world, U.K. spelling and usage > are the norm. > > Would it be difficult to add the other spelling as an alias? > > Just my two cents, err, tuppence, err, whatever. > -Yitz > > On Fri, Jan 16, 2015 at 12:26 PM, Simon Peyton Jones > <[email protected]> wrote: >> We don't have a solid policy. Personally I prefer English, but then I would. >> >> Simon >> >> | -----Original Message----- >> | From: ghc-devs [mailto:[email protected]] On Behalf Of Jan >> | Stolarek >> | Sent: 16 January 2015 10:19 >> | To: [email protected] >> | Subject: American vs. British English >> | >> | I just realized GHC has data types named FamFlavor and FamFlavour. >> | That said, is there a policy that says which English should be used in >> | the source code? >> | >> | Janek >> | >> | _______________________________________________ >> | ghc-devs mailing list >> | [email protected] >> | http://www.haskell.org/mailman/listinfo/ghc-devs >> _______________________________________________ >> ghc-devs mailing list >> [email protected] >> http://www.haskell.org/mailman/listinfo/ghc-devs > _______________________________________________ > ghc-devs mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list [email protected] http://www.haskell.org/mailman/listinfo/ghc-devs
