Back to home page

DOS ain't dead

Forum index page

Log in | Register

Search:  
Back to the forum
Board view  Mix view

(My) fork of 8086 Assembler for DOS (Announce)

posted by DosWorld, 28.12.2020, 14:00
(edited by DosWorld on 28.12.2020, 14:47)

> OK, thanks for example.
> So only the object file in OMF format can be linked directly by TP without
> external tools and C-- supports this format. And how about OBJ files
> produced by TurboC and TurboAssembler? Those are also OMF or different
> format that cannot be used this way?
Yes, this is the same obj/omf. In DOS was available only one obj format - omf. All 99% of commercial compilers and linkers in 80x and 90x understand obj in omf format. It was a industrial standart - the same as coff (for obj) now.

Yes, TC and TASM produce same obj/omf format and for linking uses TLINK - this is obj/omf linker. Microsoft has the same toolchain - MASM + LINK and they also work with obj/omf. Yes, if i am not wrong Turbo C had "pascal" (and "far") keywords - so they could be linked with TP. TASM could be linked with TP/TC with zero problem - this is native case.

Dinosaurs Small C + Small Assembler also uses obj/omf. Also, imho, many OS/2 compilers also work with obj/omf (omf have extensions for 32bit segments, but this is not the same as coff).

So, if you want create near to professional grade compiler - you must work with obj/omf. If you want deliver libraries - you must do it with obj/lib in omf format.

Only DJGPP can don't understand OFM format (not sure, IMHO), but this is for me "alien" technology (came to microcomputers from mainframes in later times). (May be "alien" is wrong word?)

---
Make DOS great again!
Make Russia small again!

Post reply
 

Complete thread:

Back to the forum
Board view  Mix view
22370 Postings in 2073 Threads, 400 registered users, 117 users online (0 registered, 117 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum