fix undefined start conditions error : https://github.com/zaach/jison-le...

[ichiriac]

An attempt to fix this issue #9

Situation before the fix :
If a start condition is not defined in headers the lexer fails without any error message

Situation with this fix :
If there is a missing start condition, the lexer triggers a console warning explaining that a start condition is not declared, and the missing start condition is declared as not inclusive (fallback behaviour)

[zaach]

Ah, thanks for the PR! A better error message is definitely needed here, though I think we should fail hard rather than create an implicit rule.

As for the other bug, I'd like to understand what the issue is better– there might be a more general fix needed to handle windows line endings.

[ichiriac]

Glad to help you !

I'm agree with you, you can also fail hard. I've started to learn flex & bison syntax with your documentation first so, I did not knew that when you use a start condition, you MUST declare it as %x or %s. Anyway, an explicit message error would be better

For the windows EOL I did not look everywhere, but seems that the bug is just only in input function because it eats one char at time.