NASM Wishlist
=============

- Listing file support.

- Remove [INCLUDE] and [INC] for good.

- Option to specify command line options in the file? May not work
  well for -o or -f...

- Actually _do_ something with the processor, privileged and
  undocumented flags in the instruction table.

- Maybe NEC V20/V30 instructions?

- Yet more object formats.
  * Do OS/2 object files have documentation?
  * What format does Watcom C use?
  * Are there any others?

- Debug information, in all formats it can be usefully done in.
  * including line-number record support.

- Symbol map in binary format. Format-specific options...

- Sort out near/far commons in OBJ, and aligned commons in ELF.

- PIC support in ELF?

- DLL export/import in Win32. Possibly Win16 extensions to OBJ, as
  well.

- REDESIGN: Think about EQU dependency, and about start-point
  specification in OBJ. Possibly re-think directive support.

- Think about a wrapper program like gcc? Possibly invent a _patch_
  for gcc so that it can take .asm files on the command line?

- If a wrapper happens, think about adding an option to cause the
  resulting executable file to be executed immediately, thus
  allowing NASM source files to have #!... (probably silly)

Things to remember about if they recur in the future
====================================================

Fixup-overflow messages from Borland linker. Current suspicion is
that both complainants were using the wrong memory model.

Segfault relating to LCC 3.5 on Jules' machine. Never recurred on my
box, and nobody else has moaned about similar problems.
