You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for your time and effort on all your amazing projects!
I recently switched to reflex as the main lex implementation on my system, and things have been smooth until I stumbled upon this missing flag --header-file when attempting to build kbd.
Attempting to ./configure then make on kbd throws the following error:
I never thought about that. It wouldn't help with the main use I make for lexers (in vile). Some thoughts:
it would have been nice to use the same option letters that yacc uses, but flex's -d and yacc's -d are already assigned
on the other hand, I'd prefer to not lock into long options for various reasons
aside from dithering over option assignments, there's the question of how it might be used. I see you're using some bison-specific %option lines. Perhaps (with the header option) reflex might not work in that application. (If it does, generating the header is not a big effort).
Hey there Mr. Thomas,
Thank you for your time and effort on all your amazing projects!
I recently switched to
reflex
as the mainlex
implementation on my system, and things have been smooth until I stumbled upon this missing flag--header-file
when attempting to buildkbd
.Attempting to
./configure
thenmake
onkbd
throws the following error:It appears to be complaining about a missing flag
--header-file
thatflex
supports.Is this intended behavior?
Thanks again for your time!
The text was updated successfully, but these errors were encountered: