<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 23, 2017 at 4:10 PM, Ben Franksen <span dir="ltr"><<a href="mailto:ben.franksen@online.de" target="_blank">ben.franksen@online.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div id="gmail-:237" class="gmail-a3s gmail-aXjCH gmail-m159cd2bc6ffa7db3">I have no doubt that there are companies and/or lawyers like that. What<br>
I doubt is that this is the overwhelming majority, as you seemed to<br>
suggest ("...most corporate lawyers..."). All the evidence you and Sven<br>
provided is merely anecdotal.</div></blockquote></div><br>Mrrr. I was trying to back that off a bit; the real issue is not that it's "most", it's "enough to make ghc problematic". The last thread about cpphs (quick search gets me <a href="https://mail.haskell.org/pipermail/ghc-devs/2015-May/009106.html">https://mail.haskell.org/pipermail/ghc-devs/2015-May/009106.html</a> from the middle of it and containing a decent summary) indicated that a significant number of high profile Haskell users would be forced to drop Haskell if cpphs went into ghc, because they'd have to face the uphill battle of getting corporate lawyers to okay it again.</div><div class="gmail_extra"><br></div><div class="gmail_extra">"Just do it and fix the fallout afterward" is not a solution; once in, those lawyers would think twice about reinstating ghc if it were subsequently removed, because that's the safe stance legally speaking.</div><div class="gmail_extra"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>