> On 18 Apr 2018, at 15:56, Kaz Kylheku wrote:
>
> What I'm saying is that Flex 2.5.35 in an Ubuntu installation I'm
> using has this behavior:
>
> /* comment */
> %{
> #include "header.h"
> %}
> /* ... */
>
> The header comment is propagated to the lex.yy.c file. It's not at the top
> of
On 2018-04-18 01:36, Hans Åberg wrote:
On 18 Apr 2018, at 02:16, Kaz Kylheku wrote:
(Side note: this is a different behavior from GNU Flex, which passes
through
the comment even if is outside of the %{ ... %} block).
No, it doesn't, not in my code. In some circumstances, one might leave
out
> On 18 Apr 2018, at 11:19, Frank Heckenbach wrote:
>
> Hans Åberg wrote:
>
>> Indeed. Others, may not want to patch their installations even it
>> they can, as it may cause problems for other packages. Say if one
>> writes package that uses a standard Bison installation, then it
>> would be d
Hans Åberg wrote:
> Indeed. Others, may not want to patch their installations even it
> they can, as it may cause problems for other packages. Say if one
> writes package that uses a standard Bison installation, then it
> would be dangerous to patch it up with an experimental one.
Not really dang
> On 18 Apr 2018, at 10:03, Frank Heckenbach wrote:
>
> Hans Åberg wrote:
>
>>> On 14 Apr 2018, at 10:19, Frank Heckenbach wrote:
>>>
>>> Hans Åberg wrote:
>>>
>> Before it gets integrated into the Bison distribution, you might
>> want to put it in the package source directory.
> On 18 Apr 2018, at 02:16, Kaz Kylheku wrote:
>
> On 2018-04-16 13:27, Hans Åberg wrote:
>>> On 16 Apr 2018, at 22:01, Kaz Kylheku wrote:
>>> When Bison turns a .y file into a y.tab.c, it removes any license
>>> header from the .y file, and asserts its own license over the file
>>> (which com
Hans Åberg wrote:
> > On 14 Apr 2018, at 10:19, Frank Heckenbach wrote:
> >
> > Hans Åberg wrote:
> >
> Before it gets integrated into the Bison distribution, you might
> want to put it in the package source directory.
> >>>
> >>> I won't for my code (but you, or anyone else, may wan
