Number: 191

Date: 19-Mar-84 17':09':40

Submitter: Sannella.PA

Source: Sheil.pa

Subject: EVALV should have release-stack-ptr flag

Assigned To: Masinter.pa

Attn: 

Status: Closed

In/By: Harmony

Problem Type: Documentation

Impact: Moderate

Difficulty: Easy

Frequency: Everytime

Priority: Unlikely

System: Language Support

Subsystem: Stack and Interpreter

Machine: 

Disk: 

Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: '
["Sannella" "20-Aug-84 19':16':25" Attn': Status':(Fixed->Closed) In/By': Description':]

Description: '
Date': 19 Mar 84 09':39 PST'
From': Sheil.pa'
Subject': Lisp': EVALV': Request for info'
To': lispsupport'
'
Does EVALV release its stack pointer arg? Why is there not a release flag, like for ENVEVAL etc etc?'
'
Beau'
-----'
Date': 19 Mar 84 17':14 PST'
From': Masinter.pa'
Subject': Re': AR 191': EVALV should have release-stack-ptr flag'
In-reply-to': LispSupport.pa''s message of 19 Mar 84 17':10':13 PST (Monday)'
To': LispSupport.pa'
cc': SHEIL'
'
EVALV doesn''t have a RELEASEFLG because it doesn''t  ever give up control. The reason ENVEVAL and friends have RELEASEFLG is because they can never return. With EVALV, you can say (PROG1 (EVALV var stkp) (RELSTK stkp)]'
'
Change AR to':'
'
Status': Wish'
Priority': Unlikely'
Difficulty': Easy'
'
-----'
Date': 19 Mar 84 18':20 PST'
From': Sheil.pa'
Subject': Re': AR 191': EVALV should have release-stack-ptr flag'
In-reply-to': Masinter.pa''s message of 19 Mar 84 17':14 PST'
To': Masinter.pa'
cc': LispSupport.pa'
'
OK. But the rationale should be in the manual. Personally, I find the discrepancy in style irritating.'
'
Beau'
'
-----'
'
Date':  6 Apr 84 16':43 PST'
From': Masinter.pa'
Subject': AR#191, EVALV'
To': LispSupport'
cc': Sheil'
'
EVALV now has a ''release'' flag. Documentation in manual updated. Mark AR as FIXED.'


Workaround: 

Test Case: 

Edit-By: Sannella

Edit-Date: 20-Aug-84 19':16':26