(c) James Noble 
 2003

this file is to hold various info on the project

information pertaining to the maps handling of the enemies:
	with each section of the map currently in there may be enemies.
	if this section of the map is left the enemies will be given the time to heal
	 their wounds.
	this will be because upon entering a section of the map, if there are enemies,
	 there will be a construction of a linked list to hold the enemies structures.
	if an enemy is killed he will be removed from the current list, and the number
	 of enemies in the section will be decremented.
	so it is of little worth to not finish of an enemy once found in a sector, since
	 upon returning he will be at full health.
that was as of Aug 20th 2003 ... it's changed a bit since then

basically, most all info is in the header files ... 'rule 5: data dominates'
(Oct 22, 2003)

Well here it is:

*** BUGS ***
BUG 0000 : FIXED : 12/24/03 1:49AM
	map_enem.c - 12/08/2003 22:17 CST
	if a fresh matrix file is made in the mapmaker (or if all entries are 
	deleted) the mapmaker can save a new matrice file just fine.
	however, the mapmaker cannot load up a file, add an entry, and then save
	this file ... a seg fault results

BUG 0001 :
	ok, bug 0000 is gone, but a new one is in it's place
	for one, the system(rm .matr*_*) doesn't work for choice 4 in map_enem.c
	also, map_enem.c still doesn't add new entries and save them properly
	this may very well be a problem that exists in init_enemies() (enemies.c)
	so, anyways, time for bed - ENTRY (12/24/03 1:51AM)

*** TODO ***

0000. ) 
	Change 'print_activity.c':get_newmap to use 'map.info' for finding which
	maps to use.  Though later, this will be read in when the player loads
	his saved game (this info is from 'map_info.h', more particularly
	struct map { ... } the_map; and row_loc, col_loc).  I will have to
	add into that file some entry for which map to use. Probably named
	map_loc.
	
	12/24/03 12:42AM - I'm one step closer, the mapmaker now keeps entries of
	maps in the map.info file properly.  This one took some time, since i'd never
	worked with fseek & company. A new fn was written for this in mapmaker.c
	called 'check_map_info ()'.

0001. ) 
	Bring about full use of enemies.c: especially init() and de_init()
	clean up mapmaker.c, map_enem.c & enemies.c

0002. )
	Setup a .h file that has definitions for exit values.
	I won't do this until i am actually using a debugger.
	I don't know much about gdb, so for now it doesn't really matter.

0003. )
	mapmaker needs to create the directories better, right now it's all f***ed up

