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

We don't have a solid policy. Personally I prefer English, but then I would. Simon | -----Original Message----- | From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Jan | Stolarek | Sent: 16 January 2015 10:19 | To: ghc-devs@haskell.org | 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 | ghc-devs@haskell.org | http://www.haskell.org/mailman/listinfo/ghc-devs

If one has to choose an English, then it should be English English.
On 16 January 2015 at 20:26, Simon Peyton Jones
We don't have a solid policy. Personally I prefer English, but then I would.
Simon
| -----Original Message----- | From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Jan | Stolarek | Sent: 16 January 2015 10:19 | To: ghc-devs@haskell.org | 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 | ghc-devs@haskell.org | http://www.haskell.org/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs

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
We don't have a solid policy. Personally I prefer English, but then I would.
Simon
| -----Original Message----- | From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Jan | Stolarek | Sent: 16 January 2015 10:19 | To: ghc-devs@haskell.org | 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 | ghc-devs@haskell.org | http://www.haskell.org/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs

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
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
wrote: We don't have a solid policy. Personally I prefer English, but then I would.
Simon
| -----Original Message----- | From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Jan | Stolarek | Sent: 16 January 2015 10:19 | To: ghc-devs@haskell.org | 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 | ghc-devs@haskell.org | http://www.haskell.org/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs

Best would be spelling suggestion for language extensions much like we get
for other names.
On Mon, Jan 26, 2015 at 10:17 AM, Boespflug, Mathieu
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
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
wrote: We don't have a solid policy. Personally I prefer English, but then I would.
Simon
| -----Original Message----- | From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Jan | Stolarek | Sent: 16 January 2015 10:19 | To: ghc-devs@haskell.org | 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 | ghc-devs@haskell.org | http://www.haskell.org/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs

| 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.
It's too late. We have aliases for lots of pragmas and language extensions, and probably should have one for this too, if only for consistency.
(If someone wants to be consistent the other way, and builds a consensus for taking them all out, that's fine by me too.)
Meanwhile, would someone like to add the alias for GeneralisedNewtypeDeriving?
Simon
| -----Original Message-----
| From: Boespflug, Mathieu [mailto:m@tweag.io]
| Sent: 26 January 2015 18:17
| To: gale@sefer.org
| Cc: Simon Peyton Jones; ghc-devs@haskell.org
| Subject: Re: American vs. British English
|
| 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
participants (6)
-
Boespflug, Mathieu
-
Greg Weber
-
Jan Stolarek
-
Simon Peyton Jones
-
Sophie Taylor
-
Yitzchak Gale