Age | Commit message (Collapse) | Author | Files | Lines |
|
* It's actually the time of running ./configure that will be used.
* On OpenWatcom, it does not seem to be possible to set variables
based on external processes, so you will still have to update
AUTO_DATE in teco.h when releasing for DOS.
|
|
workaround
Also, we increased the maximum size of objects to be put into the "far data" section,
which significantly decreases the DOS binary size.
|
|
* fixes at least <FS>, which has been broken since b5325e00c402ec18034da4b4a4aaaefa87bb1fef.
* but probably many other commands as well in the DOS version when working with
"very large" documents
* now compiles cleanly with -Wsign-compare
|
|
* This is not done by the shell in DOS.
* As a side effect, we support all of the Csh-like constructs like
{a,b,c} in contrast to Watcom's fnmatch().
|
|
|
|
* The magic field is now always called __magic.
* Saves some memory, which is important especially on MS-DOS.
|
|
In particular, this will work on MS-DOS, albeit inefficiently.
You also cannot generically redirect stderr on COMMAND.COM.
|
|
* This allows handling files >64kb even on 16-bit DOS.
* A few flags fields could be squashed into bitfields.
* The buffer overview (0EB) has been adapted for DOS.
We can only show the total amount of allocated
memory (as by tecmem.c) for the time being.
Unfortunately, we don't have a total amount of available
memory since _memavl() is for small data models and
the sbrk() apparently doesn't grow.
|
|
This will save a lot of stack space and sometimes heap space on DOS.
|
|
This is done via 10h interrupts and special memory regions.
The alternative would have been to use set the cursor to 9999,9999
and query the cursor position via ANSI escape sequences.
|
|
It can be cross-compiled or compiled natively on 32-bit DOS
with OpenWatcom C v1.9.
Compiling on an 8086 might be possible later on - but we would
have to add support for some ancient ANSI C compiler.
|
|
Also avoid old-school function declarations without parameters (`void foo();`).
This is unnecessarily loosing type safety.
|
|
|
|
this is possible since BITS_PER_INT is not used in any preprocessor
expression
|
|
* should be configurable using ./configure (disabled by default)
|
|
* adapted Doxygen config file
|
|
|
|
|