It is not my experience that encouraging stagnation in library APIs
will either reduce CPP or improve the community.
My project modules using CPP:
0/12
0/6
3/9 - Changes to base/tagged, conditionally including expensive
code needed by few users
10/116 - gmp arch specific issues, RecursiveDo vs DoRec,
bitSizeMaybe, debug trace
0/7
4/5 - Platform specific code selection
0/1
0/7
1/4 - Architecture specific unsafeness for performance gains
5/207 - File and line number enhanced error messages
0/1
On Fri, Jan 9, 2015 at 2:45 PM, Andrey Chudnov
Johan, I hear and agree. Even though I've never used CPP in my packages, I've read code that does ---and it's horrible. And I, too, have experienced new GHC stable versions breaking foundational libraries, including Cabal. But, my impression was that most of these breakages are due to certain GHC extensions being deprecated, and not because the compiler stops respecting the standard. Is my understanding correct? If so, then why not disable extensions and limit yourself to Haskell 2010? Yes, you get used to the good stuff quickly, and it's painful to give it up --- but isn't that what standards are for?
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe