Number: 1625

Date: 12-Jul-84  2':41':36

Submitter: le.pasa

Source: Patty Poduska (Poduska.pasa)

Subject: Loading WHEREIS.DCOM sometimes gives File not found WHEREIS.HASH error

Assigned To: RELEASE


Status: Fixed


Problem Type: Bug

Impact: Annoying

Difficulty: Easy

Frequency: Intermittent

Priority: Perhaps

System: Programming Environment

Subsystem: File Package



Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: the WHEREIS library package now looks on LISPUSERSDIRECTORIES for the files in the value of WHEREIS.HASH. Hopefully this is documented in the WHEREIS library package documentation.'
["masinter" "27-Aug-84 23':40':43" Assigned% To': Attn': Status':(Open->Fixed) Disposition':]

Description: '
        WHEREIS randomly behaves strangely.'
	When loading the .DCOM file':'
	appears.  Opening and closing WHEREIS.HASH'
	explicitly does not work. (ex. CLOSEALL  and'
	CLOSEF don''t work when WHEREIS.HASH is'
	open; OPENFILE doesn''t open it when it is closed.'
Date': 11 JUL 84 22':44 PDT'
Subject': AR#1625, WHEREIS package bug'
To':   le.pasa, poduska.pasa'
cc':   raim.pasa, LispSupport, kaplan'
Similar comments about the "Subject': " field apply to this AR.'
In this case, could you see what version of WHEREIS.HASH it is trying to open where? '
It is probably the case that WHEREIS.HASH attempts to talk to a central ''whereis'' file. '
(I''m not the author of the current WHEREIS package. You might want to append this note to the current AR.)'
((in Unix-land, packages which have ''known deficiencies'' get the documentation about their known deficiencies appended to the end of their documentation. Maybe some note about this belongs in the WHEREIS documentation. Do you have the capability/charter of updating [eris]<LispUsers>WHEREIS documentation?))'
Date': 12 JUL 84 19':24 PDT'
Subject': WHEREIS problem'
To':   LispSupport'
cc':   Poduska.pasa'
I fixed a problem in WHEREIS which happened when it couldn''t find the WHEREIS.HASH file -- it now prints out a warning message. (It used to do something fairly random.)'


Test Case: 

Edit-By: masinter

Edit-Date: 27-Aug-84 23':40':45