Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-03-12 05:43:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

DJGPP support added

Browse Source
This commit is contained in:
Juan Manuel Guerrero
2002-02-13 16:13:31 +00:00
parent 9cbe3c4878
commit cc20bc3166
6 changed files with 96 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
doc/bison.texinfo
View File

@@ -304,6 +304,8 @@ Invoking Bison
* Bison Options:: All the options described in detail,
in alphabetical order by short options.
* Option Cross Key:: Alphabetical list of long options.
* Extension Limitations Under DOS:: Bison output files extension differences
depending on the DOS/Windows file system flavour used.
* VMS Invocation:: Bison command syntax on VMS.
Copying This Manual
@@ -5047,6 +5049,8 @@ will produce @file{output.c++} and @file{outfile.h++}.
in alphabetical order by short options.
* Environment Variables:: Variables which affect Bison execution.
* Option Cross Key:: Alphabetical list of long options.
* Extension Limitations Under DOS:: Bison output files extension differences
depending on the DOS/Windows file system flavour used.
* VMS Invocation:: Bison command syntax on VMS.
@end menu
@@ -5244,6 +5248,39 @@ the corresponding short option.
@end example
@end ifinfo
@node Extension Limitations Under DOS
@section Extension Limitations under DOS
@cindex extension limitations under DOS
@cindex DOS
On DOS/Windows 9X systems the file name extensions of the output files,
like @file{.tab.c}, that may be used depend on the file system in use.
The plain DOS file system has limited file name length, does not allow
the use of a set of certain illicit characters and does not allow more
than a single dot in the file name.
The DJGPP port of @code{bison} will detect at runtime if (LFN) long file name
support is available or not. LFN support will be available in a DOS session
under Windows 9X and successors. Windows NT 4.0 needs a special LFN driver
(@file(ntlfn08b.zip) or later available at any simtelnet mirror in the /v2misc
dir) for proper LFN support in a DOS session. If LFN support is available the
DJGPP port of @code{bison} will use the standard POSIX file name extensions
of the output files. If LFN support is not available, then the DJGPP port
of @code{bison} will use DOS specific file name extensions.
@noindent This table summarizes the used extensions:
@multitable @columnfractions 0.1 0.45 0.45
@item @tab LFN extension (Win9X) @tab SFN extension (plain DOS)
@item @tab @file{.tab.c} @tab @file{_tab.c}
@item @tab @file{.tab.h} @tab @file{_tab.h}
@item @tab @file{.tab.cpp} @tab @file{_tab.cpp}
@item @tab @file{.tab.hpp} @tab @file{_tab.hpp}
@item @tab @file{.output} @tab @file{.out}
@item @tab @file{.stype.h} @tab @file{.sth}
@item @tab @file{.guard.c} @tab @file{.guc}
@end multitable
@node VMS Invocation
@section Invoking Bison under VMS
@cindex invoking Bison under VMS