lex(1) [centos man page]
FLEX(1) User Commands FLEX(1) NAME
flex - the fast lexical analyser generator SYNOPSIS
flex [OPTIONS] [FILE]... DESCRIPTION
Generates programs that perform pattern-matching on text. Table Compression: -Ca, --align trade off larger tables for better memory alignment -Ce, --ecs construct equivalence classes -Cf do not compress tables; use -f representation -CF do not compress tables; use -F representation -Cm, --meta-ecs construct meta-equivalence classes -Cr, --read use read() instead of stdio for scanner input -f, --full generate fast, large scanner. Same as -Cfr -F, --fast use alternate table representation. Same as -CFr -Cem default compression (same as --ecs --meta-ecs) Debugging: -d, --debug enable debug mode in scanner -b, --backup write backing-up information to lex.backup -p, --perf-report write performance report to stderr -s, --nodefault suppress default rule to ECHO unmatched text -T, --trace flex should run in trace mode -w, --nowarn do not generate warnings -v, --verbose write summary of scanner statistics to stdout Files: -o, --outfile=FILE specify output filename -S, --skel=FILE specify skeleton file -t, --stdout write scanner on stdout instead of lex.yy.c --yyclass=NAME name of C++ class --header-file=FILE create a C header file in addition to the scanner --tables-file[=FILE] write tables to FILE Scanner behavior: -7, --7bit generate 7-bit scanner -8, --8bit generate 8-bit scanner -B, --batch generate batch scanner (opposite of -I) -i, --case-insensitive ignore case in patterns -l, --lex-compat maximal compatibility with original lex -X, --posix-compat maximal compatibility with POSIX lex -I, --interactive generate interactive scanner (opposite of -B) --yylineno track line count in yylineno Generated code: -+, --c++ generate C++ scanner class -Dmacro[=defn] #define macro defn (default defn is '1') -L, --noline suppress #line directives in scanner -P, --prefix=STRING use STRING as prefix instead of "yy" -R, --reentrant generate a reentrant C scanner --bison-bridge scanner for bison pure parser. --bison-locations include yylloc support. --stdinit initialize yyin/yyout to stdin/stdout --noansi-definitions old-style function definitions --noansi-prototypes empty parameter list in prototypes --nounistd do not include <unistd.h> --noFUNCTION do not generate a particular FUNCTION Miscellaneous: -c do-nothing POSIX option -n do-nothing POSIX option -? -h, --help produce this help message -V, --version report flex version SEE ALSO
The full documentation for flex is maintained as a Texinfo manual. If the info and flex programs are properly installed at your site, the command info flex should give you access to the complete manual. flex 2.5.36 July 2012 FLEX(1)
Check Out this Related Man Page
sane-find-scanner(1) General Commands Manual sane-find-scanner(1) NAME
sane-find-scanner - find SCSI and USB scanners and their device files SYNOPSIS
sane-find-scanner [-h|-?] [-v] [-q] [-f] [devname] DESCRIPTION
sane-find-scanner is a command-line tool to find SCSI and some USB scanners and determine their Unix device files. It's part of the sane- backends package. For SCSI scanners, it checks the default generic SCSI device files (e.g., /dev/sg0) and /dev/scanner. The test is done by sending a SCSI inquiry command and looking for a device type of "scanner" or "processor" (some old HP scanners seem to send "processor"). So sane-find- scanner will find any SCSI scanner connected to those default device files even if it isn't supported by any SANE backend. For USB scanners, first the USB kernel scanner device files (e.g. /dev/usb/scanner0), /dev/usb/scanner, and /dev/usbscanner are tested. The files are opened and the vendor and device ids are determined if the operating system supports this feature. Currently USB scanners are only found this way if they are supported by the Linux scanner module or the FreeBSD or OpenBSD uscanner driver. After that test, sane- find-scanner tries to scan for USB devices found by the USB library libusb (if available). There is no special USB class for scanners, so the heuristics used to distinguish scanners from other USB devices is not perfect. sane-find-scanner will even find USB scanners, that are not supported by any SANE backend. sane-find-scanner won't find parallel port scanners, or scanners connected to proprietary ports. OPTIONS
-h, -? Prints a short usage message. -v Verbose output. If used once, sane-find-scanner shows every device name and the test result. If used twice, SCSI inquiry informa- tion and the USB device descriptors are also printed. -q Be quiet. Print only the devices, no comments. -f Force opening all explicitely given devices as SCSI and USB devices. That's useful if sane-find-scanner is wrong in determing the device type. devname Test device file "devname". No other devices are checked if devname is given. EXAMPLE
sane-find-scanner -v Check all SCSI and USB devices for available scanners and print a line for every device file. sane-find-scanner /dev/scanner Look for a (SCSI) scanner only at /dev/scanner and print the result. SEE ALSO
sane(7), sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1), sane-"backendname"(5) AUTHOR
Oliver Rauch, Henning Meier-Geinitz and others SUPPORTED PLATFORMS
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel, libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the vendor and device ids only works with Linux or libusb. SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris, FreeBSD, NetBSD, OpenBSD, and HP-UX. BUGS
No support for parallel port scanners yet. 15 Sep 2002 sane-find-scanner(1)