<div dir="ltr">On Sat, Jul 6, 2013 at 2:55 PM, Ian Lynagh <span dir="ltr"><<a href="mailto:ian@well-typed.com" target="_blank">ian@well-typed.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Jul 05, 2013 at 12:14:06PM -0500, Nicolas Frisby wrote:<br>
><br>
> I've been trying to let a statically-linked compiler shares its FastString<br>
> table with plugins.<br>
<br>
</div>Why not use a dynamically linked compiler?<br></blockquote><div><br></div><div style>My main concern with this option is having the plugins that need FastString support work with an out-of-the-box ghc. If my plugin's prerequisite is "first, go rebuild another copy of GHC", my plugin might as well not be a plugin.</div>
<div style><br></div><div style>I'm still hoping for more responses to my other email on this topic, but it's starting to seem that having the out-of-the-box ghc be a dynamically link against libHSghc is not necessarily likely on all platforms that support Core plugins.</div>
<div style><br></div><div style>Thanks.</div></div></div></div>