RE: [Template-haskell] RE: Template Haskell...
Trouble is, that's thoroughly awkward one to implement, because it means compiling the transitive closure of all the things in this module referred to by the bit you are running. I'm sure it's doable, but I'm not looking fwd to it. S | -----Original Message----- | From: template-haskell-bounces@haskell.org [mailto:template-haskell-bounces@haskell.org] On | Behalf Of Alastair Reid | Sent: 31 October 2003 17:21 | To: Simon Peyton-Jones; MR K P SCHUPKE; template-haskell@haskell.org | Subject: Re: [Template-haskell] RE: Template Haskell... | | The other big thing on my wish list is to relax the requirement that templates | go in a separate module from code that invokes the template. | | In Template Greencard, this is a major hassle because you have to put the code | to handle C types (you typically define a new template for each C type) in a | separate module from the code to handle C functions. | | -- | Alastair Reid | | _______________________________________________ | template-haskell mailing list | template-haskell@haskell.org | http://www.haskell.org/mailman/listinfo/template-haskell
On Friday 31 October 2003 5:24 pm, Simon Peyton-Jones wrote:
Trouble is, that's thoroughly awkward one to implement, because it means compiling the transitive closure of all the things in this module referred to by the bit you are running. I'm sure it's doable, but I'm not looking fwd to it.
I can see that compiling a module one set of declaration groups at a time won't be much fun but given the way you split modules into lists of declaration groups separated by top-level splices, it seems easy enough to know what to compile: You have to compile all the code above the current top-level splice or declaration group. -- Alastair Reid
participants (2)
-
Alastair Reid -
Simon Peyton-Jones