RE: Problems with Template Haskell

| This is a bit cumbersome.  Could there be some way of wrapping the
whole
| quasi-quotation to stop it from being looked at in any way, except
what
| is strictly necessary for converting it to a Q Dec or Q Exp, unless
and
| until it is actually spliced?  In fact, I for one would prefer that to
be
| the default ...

Well I definitely don't want it to be the default, bit it would
certainly be possible to implement.  The syntactic issues are the most
bothersome ones...
        [ee| .... |]
        [dd| ...  |]
perhaps?  Or what would you suggest?>

| With "dyn" there's the problem that the module name and name of "dyn"
have
| changed from ghc6 to ghc6.3.  Meaning (a) without CPP I can't import
| Language.Haskell.THSyntax (6.0) / Language.Haskell.TH (6.3); (b) I
can't refer to
| dyn in the first place anyway.  While with CPP it all seems so easy.

Well, TH is indeed changing whereas cpp is not.  That's the trouble with
living on the bleeding edge.


| Of course (a) is an instance of a more general problem -- that we
can't
| use Template Haskell to select between import declarations.  It would
be nice
| if we could.

I think it should be possible for a TH decl to include both import and
export decls.
(an export decl would, in effect, add something to the export list).
Not done yet though.


| Am I doing the wrong thing here?  Should I simply give up on the idea
of
| replacing cpp with Template Haskell?

I hope you don't go back to cpp.   It's very helpful having real users
for TH.  But not all of your desires will be implemented at once.  So
far we have:
        - access to -D/U flags
        - un-type-checked quotes
        - import and export in TH quotes

Is that it?  Care to prioritise?  What with Xmas and then POPL, the next
month or two look a bit fragmented.

Simon