Back to home page

DOS ain't dead

Forum index page

Log in | Register

Search:  
Back to the forum
Board view  Mix view

FASM can't brew (!) OMF ".OBJ" files OBJCONV port it away (Announce)

posted by DOS386, 02.01.2009, 10:39

Rugxulo wrote:

> And having Agner's OBJCONV (sorely needed for a long time) only gives
> yet another excuse for him not to implement it.
Does it really help ??? How do you use it to get 16-bit OMF from FASM ?

> OMF is really only necessary for linking between HLLs and assembly
That's how I also see the thing ...

> Linker can be useful/necessary if no HLLs are involved at all.
Closed source pre-brewed LIB then.

> They are even useful if there's just a single module to be linked to a binary.
Please explain how. How half-done work (OBJ) can be better then fully done (EXE ready to run/crash) ?

> Asm is less portable. An assembler is among those kind of tools where the
> higher degree of portability of C is a REAL advantage.
I see no point in porting JAWASM or FASM to some 64-bit only BIG endian CPU ... but feel free to do :-D

> A second disadvantage is that a self-compiling tools can worsen the effect
> of undetected bugs. If a buggy tool is used for compilation, pretty strange
> effects are likely to occur, sometimes very hard to fix.
This assumes that you have many very mature C compilers available ... and even then, FASM's selfcompiling work is easy to check and debug.

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Post reply
 

Complete thread:

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