Number: 749 Date: 19-Apr-84 5':25':12 Submitter: le.pasa Source: Mark Rosenstein -Wogulis.pasa Subject: Want TTYIN to pay attention to (RAISE T) Assigned To: Attn: vanMelle.pa Status: Open In/By: Problem Type: Bug Impact: Annoying Difficulty: Moderate Frequency: Everytime Priority: Unlikely System: Text Subsystem: TTYIN Machine: Disk: Lisp Version: Fugue4, Fugue6 Source Files: Microcode Version: Memory Size: File Server: Server Software Version: Disposition: ' [4/18/84 tl': changed description of AR according to VanMelle message]' ["vanMelle" "23-Aug-84 14':52':22" Status':(Wish->Open)] Description: ' (JW 4/18/84': I have verified that these bugs are as reported by Mark Rosenstein)' ' Return-Path': mbr@nprdc' Received': from nprdc (NPRDC.ARPA) by Xerox.ARPA ; 13 APR 84 15':24':38 PST' Date': 13 Apr 84 09':10':27 PST' From': Mark Rosenstein ' Reply-To': mbr@nprdc.ARPA' To': 1100support.pasa' Subject': bug reports' Cc': mbr@nprdc.ARPA, mccand@nprdc.ARPA' ' machine':dorado' version':Fugue 4' ' Goal that lead to the following bugs': Trying to find if there' was a way to make interlisp case insensitive.' ' Problem 1': (GETRAISE T)' Problem': enters Raid' ' Raid': Called from Lisp. Error with Interrupts off' ' Lisp Stack' ' 1. Raid' 2. \Lisperror' 3. \Gttermtable' 4. Raise' 5. Getraise' etc.' ' Yes I know T is not a legal ttbl, but was suprised when lisp' broke. ' ' Problem 2': (RAISE T) doesn''t seem to work' Problem': seems to have same effect as (RAISE 0).' ' (RAISE T) doesn''t seem to work.' -----' ' Date': 18 Apr 84 12':49 PST' From': vanMelle.pa' ...' Problem 2': Indeed, (RAISE T) and (RAISE 0) are treated identically by TTYIN. If your LISPXREADFN is instead READ, you will notice the difference. ' Workaround: Test Case: Edit-By: vanMelle Edit-Date: 23-Aug-84 14':52':23