On Sat, Jul 6, 2013 at 2:55 PM, Ian Lynagh wrote:
> On Fri, Jul 05, 2013 at 12:14:06PM -0500, Nicolas Frisby wrote:
> >
> > I've been trying to let a statically-linked compiler shares its
> FastString
> > table with plugins.
>
> Why not use a dynamically linked compiler?
>
My main concern with t
On Sat, Jul 6, 2013 at 2:55 PM, Ian Lynagh wrote:
> On Fri, Jul 05, 2013 at 12:14:06PM -0500, Nicolas Frisby wrote:
> >
> > I've been trying to let a statically-linked compiler shares its
> FastString
> > table with plugins.
>
> Why not use a dynamically linked compiler?
>
I didn't stop to quest
On Fri, Jul 05, 2013 at 12:14:06PM -0500, Nicolas Frisby wrote:
>
> I've been trying to let a statically-linked compiler shares its FastString
> table with plugins.
Why not use a dynamically linked compiler?
Thanks
Ian
--
Ian Lynagh, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com
devs-bounces@**haskell.org
>> [mailto:ghc-devs-bounces@**haskell.org ]
>> *On Behalf Of *Nicolas Frisby
>> *Sent:* 05 July 2013 18:14
>> *To:* ghc-devs@haskell.org
>> *Subject:* use UniqSupply in FastString?
>>
>>
>> Does it sound reasonable to
ll.org
*Subject:* use UniqSupply in FastString?
Does it sound reasonable to change the FastString module to use a
UniqSupply instead of using that Int for generating uniques?
I've been trying to let a statically-linked compiler shares its
FastString table with plugins. Status, background info,
>
> In other words, we always "load" a tiny special plugin that does the
> 'reinitializeGlobals` call and is otherwise a noop. Since all plugins share
> the some dynamically loaded library, we just need 'reinitializeGlobals` to
> be called once, no matter how many plugins are loaded. Then the actua
any plugins are loaded. Then the actual
plugins wouldn't need to know about the whole fiasco.
I'd have to dig into the dynamic loading stuff to better estimate this… can
anyone chime in?
Thanks for the brain food!
> **
>
> Simon ****
>
> ** **
>
> *From:* ghc-d
@haskell.org
Subject: use UniqSupply in FastString?
Does it sound reasonable to change the FastString module to use a UniqSupply
instead of using that Int for generating uniques?
I've been trying to let a statically-linked compiler shares its FastString
table with plugins. Status, backgrou
Does it sound reasonable to change the FastString module to use a
UniqSupply instead of using that Int for generating uniques?
I've been trying to let a statically-linked compiler shares its FastString
table with plugins. Status, background info, options here:
http://hackage.haskell.org/trac/gh
