On Fri, May 22, 2020 at 03:16:56AM -0700, Manoj Srivastava wrote: > > On 12:19 Thursday, 21 May 2020 +0200, Bill Allombert wrote > > On Wed, May 20, 2020 at 10:03:08PM -0700, Manoj Srivastava wrote: > > > While it is true that the change was incompatible wwith what we > > > had befire, the change was made almost four and a half years ago. I > > > suspect we have gotten used to it now; and changing it back would just > > > cause issues. > > > > Is the new behaviour documented now ? > > This is needed to use yyinput() properly. > > See below. The yyinput usage is demonstrated in an example in > the info node about generating C++ scanners.
Well but this is not proper documentation, this is incidental documentation at best. Someone writing a C scanner will not read this example. Is it documented somewhere that the yyinput API has changed ? > > The commit message does give any rationale or information about this. > > > > > I guess this is the new normal? > > > > Do you mean that sacarstically ? > > What make you think that? After 4.5 years of this being the > default, stating that yyinput returning NULL is normal seems like a > statement of fact. Sorry, I always understood the expression 'the new normal' to be sarcastic in nature. Note that the time should be computed between the time the new flex is released and the time I report the problem, not between the git commit and now. Cheers, Bill.
