I agree it is a conundrum, and has made me vaguely uncomfortable from the beginning.
There is an earlier version, but it does not support unicode, which is important to a segment of users, and mandated by the Javascript language definition. If I recall correctly, the changes are pretty much in the lexer only, since it only affects identifiers and comments. Possibly the correct way to solve it is to get the utf8 branch of Alex to become the main line version. Otherwise, clone Lexer.x into a utf8 version and strip out all the unicode stuff in the current one. The resulting lexer will not support unicode though, and you will get bug reports on it. Alan On Sat, Jun 11, 2011 at 8:59 PM, Clint Adams <[email protected]> wrote: > On Sat, Jun 11, 2011 at 08:40:54PM +0200, Alan & Kim Zimmerman wrote: > > What version of GHC are you using? > > 7.0.3 > > > Also, the package can only build against a specific branch of Alex on > > github, to provide the full unicode support. > > > > Have you cloned it on github? > > Our alex is mainline with a few lines patched. > > I'm not sure what we should do here. Is there an earlier version > of language-javascript that doesn't need the forked Alex? >
