Re: flex++ and lex are synonyms for flex(1) in flex.1

2015-09-20 Thread Nicholas Marriott
The .Nm part yes, but but flex++ is not a synonym, flex generates
different output when called as flex++. This is already mentioned in the
later section on C++.


On Sat, Sep 19, 2015 at 10:29:12PM -0400, Rob Pierce wrote:
> Does this makes sense? I took the same approach used in chpass.1.
> 
> Regards,
> 
> Index: flex.1
> ===
> RCS file: /cvs/src/usr.bin/lex/flex.1,v
> retrieving revision 1.41
> diff -u -p -r1.41 flex.1
> --- flex.17 Sep 2015 15:28:06 -   1.41
> +++ flex.120 Sep 2015 02:21:13 -
> @@ -33,7 +33,9 @@
>  .Dt FLEX 1
>  .Os
>  .Sh NAME
> -.Nm flex
> +.Nm flex ,
> +.Nm flex++ ,
> +.Nm lex
>  .Nd fast lexical analyzer generator
>  .Sh SYNOPSIS
>  .Nm
> @@ -69,6 +71,12 @@ library to produce an executable.
>  When the executable is run, it analyzes its input for occurrences
>  of the regular expressions.
>  Whenever it finds one, it executes the corresponding C code.
> +.Pp
> +.Nm flex++
> +and
> +.Nm lex
> +are synonyms for
> +.Nm flex .
>  .Pp
>  The manual includes both tutorial and reference sections:
>  .Bl -ohang
> 



Re: flex++ and lex are synonyms for flex(1) in flex.1

2015-09-20 Thread Rob Pierce
On Sun, Sep 20, 2015 at 02:26:38PM +0100, Nicholas Marriott wrote:
> The .Nm part yes, but but flex++ is not a synonym, flex generates
> different output when called as flex++. This is already mentioned in the
> later section on C++.
> 
> 
> On Sat, Sep 19, 2015 at 10:29:12PM -0400, Rob Pierce wrote:
> > Does this makes sense? I took the same approach used in chpass.1.
> > 
> > Regards,
> > 
> > Index: flex.1
> > ===
> > RCS file: /cvs/src/usr.bin/lex/flex.1,v
> > retrieving revision 1.41
> > diff -u -p -r1.41 flex.1
> > --- flex.1  7 Sep 2015 15:28:06 -   1.41
> > +++ flex.1  20 Sep 2015 02:21:13 -
> > @@ -33,7 +33,9 @@
> >  .Dt FLEX 1
> >  .Os
> >  .Sh NAME
> > -.Nm flex
> > +.Nm flex ,
> > +.Nm flex++ ,
> > +.Nm lex
> >  .Nd fast lexical analyzer generator
> >  .Sh SYNOPSIS
> >  .Nm
> > @@ -69,6 +71,12 @@ library to produce an executable.
> >  When the executable is run, it analyzes its input for occurrences
> >  of the regular expressions.
> >  Whenever it finds one, it executes the corresponding C code.
> > +.Pp
> > +.Nm flex++
> > +and
> > +.Nm lex
> > +are synonyms for
> > +.Nm flex .
> >  .Pp
> >  The manual includes both tutorial and reference sections:
> >  .Bl -ohang
> > 

Ah, yes - thank you.

Since "flex++" is the same as "flex -+", how about this?

I took the wording from apropos.1.

Index: flex.1
===
RCS file: /cvs/src/usr.bin/lex/flex.1,v
retrieving revision 1.41
diff -u -p -r1.41 flex.1
--- flex.1  7 Sep 2015 15:28:06 -   1.41
+++ flex.1  20 Sep 2015 14:27:46 -
@@ -33,7 +33,9 @@
 .Dt FLEX 1
 .Os
 .Sh NAME
-.Nm flex
+.Nm flex ,
+.Nm flex++ ,
+.Nm lex
 .Nd fast lexical analyzer generator
 .Sh SYNOPSIS
 .Nm
@@ -69,6 +71,15 @@ library to produce an executable.
 When the executable is run, it analyzes its input for occurrences
 of the regular expressions.
 Whenever it finds one, it executes the corresponding C code.
+.Pp
+.Nm lex
+is a synonym for
+.Nm flex .
+.Pp
+.Nm flex++
+is a synonym for
+.Nm
+.Fl + .
 .Pp
 The manual includes both tutorial and reference sections:
 .Bl -ohang



flex++ and lex are synonyms for flex(1) in flex.1

2015-09-19 Thread Rob Pierce
Does this makes sense? I took the same approach used in chpass.1.

Regards,

Index: flex.1
===
RCS file: /cvs/src/usr.bin/lex/flex.1,v
retrieving revision 1.41
diff -u -p -r1.41 flex.1
--- flex.1  7 Sep 2015 15:28:06 -   1.41
+++ flex.1  20 Sep 2015 02:21:13 -
@@ -33,7 +33,9 @@
 .Dt FLEX 1
 .Os
 .Sh NAME
-.Nm flex
+.Nm flex ,
+.Nm flex++ ,
+.Nm lex
 .Nd fast lexical analyzer generator
 .Sh SYNOPSIS
 .Nm
@@ -69,6 +71,12 @@ library to produce an executable.
 When the executable is run, it analyzes its input for occurrences
 of the regular expressions.
 Whenever it finds one, it executes the corresponding C code.
+.Pp
+.Nm flex++
+and
+.Nm lex
+are synonyms for
+.Nm flex .
 .Pp
 The manual includes both tutorial and reference sections:
 .Bl -ohang