================================================================================
B A S T A R D                                            disassembly environment



TO-DO List
==========
There is a lot of "main functionality" coding to do to the disassembler; in 
addition, the following areas need some pretty serious attention:

 -- General
   * Make code safe for 32 and 64-bit platforms [via typedefs]
	* Make core code [API, etc] threadsafe for future expansion

 -- Database
   * Create "bookmark" table so user can mark areas of code. 
	  Link a comment to a bookmark, like in code.

 -- Documentation
   * Create generic manfile w/ "see also" for API sections:
	  bastard_addr, bastard_sec, bastard_code, bastard_sys, etc
	* Write perl script to generate manfiles from api.h sections

 -- Runtime Environment
	* Support $BASTARD_HOME env variable
	* Support ~/.bastardrc  file
	* Ditto for /etc/bastard.rc file
	* support binary input via STDIN following '--' parameter

 -- Improve command interpreter.
	* Get readline tab completion to handle API calls, SeerC keywords/funcs

 -- Libraries
   * Get Seer and Typhoon working in Solaris, BSD, Win32, and BeOS
	* Package the API, Seer, Typhoon, and the Seer & Typhoon init/cleanup
	  [perhaps via an addditional API section] into a .lib and/or .so which
	  can be used in the building of bastardesque disassemblers.

 -- Plug-in disassembler
 	* Support FPU, MMX, SIMD, etc in libi386
 	* Generalize bastard code to support other [non-i386] disasm libs
	* Allow manual assembly, maybe a bfd/as-based assembler

 -- Front-ends
	* Shell   TXT -- ghetto disassembler   
	* Ncurses GUI -- not *entirely* an IDA rip-off
	* Tk      GUI -- just because it can be done
	* Gtk     GUI -- might as well make one that looks nice
	* Xt      GUI -- 'cause we all know Gtk can't go two versions without 
	                 trashing their backwards compatibility

