If I run win_flex 2.6.3 as follows, I don't get a sample.flex.cpp file - I get an "mpat" file. In fact, if I run win_flex with "-wincompat" (note that wincompat contains the letters mpat), it only ever generates an mpat file, not the file specified by -outfile.
Is this a known bug or is it somehow unique to me??
If I run win_flex 2.6.3 as follows, I don't get a sample.flex.cpp file - I get an "mpat" file. In fact, if I run win_flex with "-wincompat" (note that wincompat contains the letters mpat), it only ever generates an mpat file, not the file specified by -outfile.
Is this a known bug or is it somehow unique to me??
win_flex.exe --outfile="sample.flex.cpp" --wincompat "sample.l"Here's verbose output:
win_flex version 2.6.3 usage statistics:
scanner options: -ivwI8 -Cem -ompat
26/2000 NFA states
8/1000 DFA states (25 words)
3 rules
Compressed tables always back-up
1/40 start conditions
17 epsilon states, 8 double epsilon states
3/100 character classes needed 1/500 words of storage, 0 reused
20 state/nextstate pairs created
12/8 unique/duplicate transitions
10/1000 base-def entries created
28/2000 (peak 27) nxt-chk entries created
2/2500 (peak 16) template nxt-chk entries created
7 empty table entries
4 protos created
2 templates created, 2 uses
8/256 equivalence classes created
1/256 meta-equivalence classes created
0 (0 saved) hash collisions, 7 DFAs equal
0 sets of reallocations needed
340 total table entries needed
Last edit: Paul Spark 2017-05-07
Sorted - this appears to be related to my virus-checker's sandboxing.