...QuickWin1
The Microsoft compilers offer the QuickWin target to allow terminal-oriented programs to run in the Windows environment
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... ``project''.2
Actually, most project-oriented systems compile the project definitions into a Makefile for use by the back-ends.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... far.3
It is not intended that this and the previous error levels will ever be used. Currently, there's no need to include handling for them.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... case.4
This happens if, in a MIME multipart posting, the final boundary cannot be found. After searching the boundary until the end-of-file, the scanner resets itself to the location of the previous boundary.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...UUFILE-_READ5
This value should only appear internally, never to be seen by an application.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... files6
Of course, this option wouldn't make sense with single-part files, since there's no ``grouping'' involved that might fail.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... files.7
Strictly speaking, the memory is of course limited. But try to fill a sensible amount with structures in the 100-byte region.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... overwritten.8
If we don't have permission to overwrite the target file, an I/O error is generated.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... details9
Actually, only the definition of UUEXPORT is needed. You could omit <config.h> and define this value elsewhere, for example in the project definitions.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... scanned10
With Microsoft compilers on MS-DOS systems, don't forget to link with setargv.obj to properly handle wildcards
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... octets11
The term ``octet'' is used here instead of ``byte'', since it more accurately reflects the 8-bit nature of what we usually call a ``byte''
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... exception12
... that is not always respected by old encoders
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... count13
Of course, encoded files must be split on line boundaries instead of at a fixed byte count.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... octets).14
Yes, there are files violating this assumption.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... text:15
In fact, this text is required by certain decoding software.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... item).16
The Filename may contain certain characters that are invalid on MS-DOS systems, like space characters
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.