Uncaught exception when adding local variables to GO, even in V6

Description

Zilf.Emit.Zap.RoutineBuilder throws an exception if we define a local variable in GO. In V6, this should probably be allowed; in other versions, we should catch the exception and issue an error.

Activity

Show:
Jesse McGrew
October 30, 2020, 9:59 PM

Jesse McGrew mentioned this issue in a commit of zilf / zilf on branch topic/default/zilf-210:

Issue error ZIL0400 (+ info ZIL0403) for "OPT" or "AUX" variables in GO.

Jesse McGrew
October 30, 2020, 10:02 PM

Jesse McGrew mentioned this issue in a commit of zilf / zilf on branch topic/default/zilf-210:

Issue error ZIL0400 (+ info ZIL0403) for "OPT" or "AUX" variables in GO.

Jesse McGrew
October 30, 2020, 10:05 PM

Jesse McGrew mentioned this issue in a merge request of zilf / zilf on branch topic/default/zilf-210:

Fix handling of local variables in GO routine

Jesse McGrew
October 30, 2020, 10:28 PM

Jesse McGrew mentioned this issue in a commit of zilf / zilf on branch branch/default:

Issue error ZIL0400 (+ info ZIL0403) for "OPT" or "AUX" variables in GO.

Jesse McGrew
October 30, 2020, 10:30 PM

Fixed in c39a855c541755601f454e3ccf6739a2febc85fc

Assignee

Jesse McGrew

Reporter

Jesse McGrew

Components

Priority

High

Fix versions

Affects versions

Configure