- `createLexer()` API added; this one will be used / is used by the updated unit tests, for one. It's meant for when you want to compile your lexers separately and then attach them to a parser later on
- `createLexer()` API added; this one will be used / is used by the updated unit tests, for one. It's meant for when you want to compile your lexers separately and then attach them to a parser later on

- export more info in the generator instance for diagnostics/userland code usage; conflict count, lalr-to-lr upgrade processing, etc. are now visible on the outside via the `conflicts` property and these extra properties when the lalr-to-lr upgrade option is enabled:
  + conflicts_have_been_fixed   (boolean)
  + conflict_productions_LU     (table)
  + conflict_states_LU          (table)

- internal `bind()` should now be more minifier-friendly (gcc?)

- `parseError` turns any fatal error report in JisonParserError exception unless a valid error class has been specified as part of the argument list. This way we ensure that *all* parser errors which get fed through `parseError` will always be recognizable as either lexer or parser errors (see below for more edits relevant to this issue)

- we do no longer *wrap* any *lexer* exception/error in a *parser* error/exception: we pass the lexer exceptions as-is, so that userland code can now, finally, use the intended quick & easy check for origin by using the `instanceof` operator: see also the updated unit tests that will be logged in the next several commits.

- for unit testing and jison compiler diagnostics: propagate the `nullable` attribute to the proper symbol set when running in LALR mode: without this edit, the `nullable()` checks in test/parser/lalr.js will be going to fail! (updated lalr test code not committed yet!)

GerHobbelt/jison,GerHobbelt/jison,GerHobbelt/jison,GerHobbelt/jison