Rewrote some phrasing in HaskLike docs
Getty Ritter
9 years ago
| 22 | 22 | |
| 23 | 23 | This module is intended for simple, ad-hoc configuration or data formats |
| 24 | 24 | that might not need their on rich structure but might benefit from a few |
| 25 | various literal formats. the 'haskLikeSpec' understands identifiers as | |
| 26 | defined by R5RS as well as string, integer, and floating-point literals | |
| 27 | as defined by the Haskell spec, but won't get any Lisp-specific vector | |
| 28 | literals or other structure. | |
| 25 | various kinds of literals. The 'haskLikeSpec' understands identifiers as | |
| 26 | defined by R5RS, as well as string, integer, and floating-point literals | |
| 27 | as defined by the Haskell spec. It does _not_ natively understand other | |
| 28 | data types, such as booleans, vectors, bitstrings, or the like. | |
| 29 | 29 | |
| 30 | 30 | -} |
| 31 | 31 | |
| 130 | 130 | |
| 131 | 131 | -- | This `SExprSpec` understands s-expressions that contain |
| 132 | 132 | -- Scheme-like tokens, as well as string literals, integer |
| 133 | -- literals, and floating-point literals. These are read | |
| 134 | -- and shown with Haskell lexical syntax, so the same set | |
| 135 | -- of values understood by GHC should be understood by this | |
| 136 | -- spec as well. This includes string escapes, different | |
| 137 |
-- |
|
| 133 | -- literals, and floating-point literals. Each of these values | |
| 134 | -- is parsed according to the lexical rules in the Haskell | |
| 135 | -- report, so the same set of string escapes, numeric bases, | |
| 136 | -- and floating-point options are available. This spec does | |
| 137 | -- not parse comments and does not understand any reader | |
| 138 | -- macros. | |
| 138 | 139 | haskLikeSpec :: SExprSpec HaskLikeAtom (SExpr HaskLikeAtom) |
| 139 | 140 | haskLikeSpec = mkSpec pHaskLikeAtom sHaskLikeAtom |