AParse the supplied text looking for Chunks. If the supplied text C does not consist of a single chunk (optionally with nested chunks < within) then the result will be a Left with a parse error.     The instances of  that are built by  ( incorporate into the implementation of  all the textual > content of the chunk. Supplying a value of the automatically  generated data type Chunk_* will use the fields in the 2 value to fill in all variables within the chunk. BParse the supplied file and generate the Haskell AST representing 8 data-type declarations of the chunks with instances of  ? incorporating the body of the chunks. Expected use is through  splicing (ghc needs -fth option for this):   $(chunksFromFile "/path/to/ templates/template_01.html") 7Parse the supplied file for chunks and return a string E representing the code generated for the data-type declarations only D of the chunks. This is useful for debugging purposes, particularly  from within ghci. E.g.   > showChunksData "/path/to/ templates/template_01.html" >> = putStrLn 7Parse the supplied file for chunks and return a string ? representing all the code generated for the chunks. This will @ return both the text of the data-declarations and the instance  < declarations. The instance declarations will often be very A large as they incorporated the text of the chunk taken from the  template.       !chunks-2007.4.18Text.HTML.ChunksText.HTML.Chunks.ParserText.HTML.Chunks.THChunkformatchunksFromFileshowChunksData showChunksAll ParsingUnitVarChr ChunkUnitContentVariableTextisText isVariable findChunks parseChunksconvertParseUnitconvertParseUnit'buildBodyAndChunks parseBeginparseEndparseVar parseBodybaseNamedeclsDdeclsF makeDataDecl makeFormattermakeFormatterB