Treat undefined variable errors consistently
Previously, a undefined variable inside a "with" caused an EvalError (which can be caught), while outside, it caused a ParseError (which cannot be caught). Now both cause an UndefinedVarError (which cannot be caught).
This commit is contained in:
		
							parent
							
								
									6b47de580f
								
							
						
					
					
						commit
						b1e3b1a4ac
					
				
					 3 changed files with 8 additions and 2 deletions
				
			
		|  | @ -16,6 +16,7 @@ MakeError(ThrownError, AssertionError) | |||
| MakeError(Abort, EvalError) | ||||
| MakeError(TypeError, EvalError) | ||||
| MakeError(ImportError, EvalError) // error building an imported derivation
 | ||||
| MakeError(UndefinedVarError, Error) | ||||
| 
 | ||||
| 
 | ||||
| /* Position objects. */ | ||||
|  |  | |||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue