1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
|
## Changes in 3.1.7:
* Add support for `%encoding` directive
(allows to control `--latin1` from inside Alex scripts)
* Make code forward-compatible with in-progress proposals
* Suppress more warnings
## Changes in 3.1.6:
* `sdist` for 3.1.5 was mis-generated, causing it to ask for Happy
when building.
## Changes in 3.1.5:
* Generate less warning-laden code, and suppress other warnings.
* Bug fixes.
## Changes in 3.1.4:
* Add Applicative/Functor instances for GHC 7.10
## Changes in 3.1.3:
* Fix for clang (XCode 5)
## Changes in 3.1.2:
* Add missing file to extra-source-files
## Changes in 3.1.1:
* Bug fixes (#24, #30, #31, #32)
## Changes in 3.1.0:
* necessary changes to work with GHC 7.8.1
## Changes in 3.0 (since 2.3.5)
* Unicode support (contributed mostly by Jean-Philippe Bernardy,
with help from Alan Zimmerman).
* An Alex lexer now takes a UTF-8 encoded byte sequence as input
(see Section 5.1, “Unicode and UTF-8”. If you are using the
"basic" wrapper or one of the other wrappers that takes a
Haskell String as input, the string is automatically encoded
into UTF-8 by Alex. If your input is a ByteString, you are
responsible for ensuring that the input is UTF-8 encoded. The
old 8-bit behaviour is still available via the --latin1
option.
* Alex source files are assumed to be in UTF-8, like Haskell
source files. The lexer specification can use Unicode
characters and ranges.
* `alexGetChar` is renamed to `alexGetByte` in the generated code.
* There is a new option, `--latin1`, that restores the old
behaviour.
* Alex now does DFA minimization, which helps to reduce the size
of the generated tables, especially for lexers that use Unicode.
|
