Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

jay(1) [debian man page]

JAY(1)							      General Commands Manual							    JAY(1)

NAME
jay - an LALR(1) parser generator for Java and C# SYNOPSIS
jay [ -tv ] [ -c ] [ -p ] [ -b file_prefix ] [ -V yyValue ] filename < skeleton DESCRIPTION
Jay reads the grammar specification in the file filename and generates an LR(1) parser for it. The parsers consist of a set of LALR(1) parsing tables and a driver routine from the file skeleton written in the Java programming language. Jay writes the parse tables and the driver routine to standard output. The following options are available: -b file_prefix The -b option changes the prefix prepended to the output file names to the string denoted by file_prefix. The default prefix is the character y. -c The -c option makes jay generate C# code instead of the default Java. -t The -t option arranges for debugging information to be incorporated in the compiled code. -v The -v option causes a human-readable description of the generated parser to be written to the file y.output. -p The -p option causes jay to print the directory in which its sample skeleton files are installed. If a project wants to use the default skeleton file included with jay, it can use this option in a makefile to find the path to the skeleton or skele- ton.cs file included with the jay distribution. If the environment variable TMPDIR is set, the string denoted by TMPDIR will be used as the name of the directory where the temporary files are created. FILES
skeleton y.output /tmp/yacc.aXXXXXX /tmp/yacc.tXXXXXX /tmp/yacc.uXXXXXX DIAGNOSTICS
If there are rules that are never reduced, the number of such rules is reported on standard error. If there are any LALR(1) conflicts, the number of conflicts is reported on standard error. HISTORY
Jay is derived from Berkeley yacc . Input conventions closely follow those of yacc ; for details, consult the parser skeleton file and the commented example included with the sources. 4.3 Berkeley Distribution May 24, 1993 / July 8, 1998 JAY(1)

Check Out this Related Man Page

YACC(1) 						    BSD General Commands Manual 						   YACC(1)

NAME
yacc -- an LALR(1) parser generator SYNOPSIS
yacc [-dlrtv] [-b file_prefix] [-o output_filename] [-p symbol_prefix] filename DESCRIPTION
Yacc reads the grammar specification in the file filename and generates an LR(1) parser for it. The parsers consist of a set of LALR(1) parsing tables and a driver routine written in the C programming language. Yacc normally writes the parse tables and the driver routine to the file y.tab.c. The following options are available: -b file_prefix Change the prefix prepended to the output file names to the string denoted by file_prefix. The default prefix is the character y. -d Cause the header file y.tab.h to be written. -l If the -l option is not specified, yacc will insert #line directives in the generated code. The #line directives let the C compiler relate errors in the generated code to the user's original code. If the -l option is specified, yacc will not insert the #line directives. Any #line directives specified by the user will be retained. -o output_filename Cause yacc to write the generated code to output_filename instead of the default file, y.tab.c. -p symbol_prefix Change the prefix prepended to yacc-generated symbols to the string denoted by symbol_prefix. The default prefix is the string yy. -r Cause yacc to produce separate files for code and tables. The code file is named y.code.c, and the tables file is named y.tab.c. -t Change the preprocessor directives generated by yacc so that debugging statements will be incorporated in the compiled code. -v Cause a human-readable description of the generated parser to be written to the file y.output. If the environment variable TMPDIR is set, the string denoted by TMPDIR will be used as the name of the directory where the temporary files are created. FILES
y.code.c y.tab.c y.tab.h y.output /tmp/yacc.aXXXXXXXXXX /tmp/yacc.tXXXXXXXXXX /tmp/yacc.uXXXXXXXXXX DIAGNOSTICS
If there are rules that are never reduced, the number of such rules is reported on standard error. If there are any LALR(1) conflicts, the number of conflicts is reported on standard error. BSD
May 24, 1993 BSD
Man Page