DOS ain't dead - open in text mode (O

open in text mode (O_TEXT) (Developers)

posted by Rugxulo , Usono, 27.02.2025, 00:29

> I think the only reason O_TEXT and O_BINARY exist
> is that some programs use read and write,
> and assume that the data handled by these routines contain
> Unix-style newlines. The more correct way to get these programs to work on
> DOS, is probably to rewrite these programs to read/write text files via
> stdio, but I realize this may not always be practical.

I'm a bit naive. I've never used creat (which GCC IA-16 lacks, see mininasm) or read. I guess they are always available on POSIX systems. (Mininasm used them for much lower footprint, and TurboC and OpenWatcom had no problems.)

creat (HelpPC)

quoting fopen (again, HelpPC):

> - text mode input, will have CRs discarded
>
> - using any of the stdio functions results in a default allocation
> of 512 bytes for the I/O buffer and the inclusion of the standard
> memory allocation functions

Post reply

Complete thread:

open in text mode (O_TEXT) - kerravon, 24.02.2025, 04:19 (Developers)
- open in text mode (O_TEXT) - kerravon, 24.02.2025, 04:24
  - open in text mode (O_TEXT) - tkchia, 26.02.2025, 16:30
    - open in text mode (O_TEXT) - Rugxulo, 27.02.2025, 00:29
    - open in text mode (O_TEXT) - kerravon, 02.03.2025, 01:30
      - open in text mode (O_TEXT) - kerravon, 02.03.2025, 01:33
      - open in text mode (O_TEXT) - tkchia, 03.03.2025, 15:09
    - open in text mode (O_TEXT) - kerravon, 02.03.2025, 01:35