V82(A): Possible bug with 'Void' and variables

Monkey Forums/Monkey Bug Reports/V82(A): Possible bug with 'Void' and variables

ImmutableOctet(SKNG)

(Posted 2014) [#1]

Hey Mark, just a heads up: If you were to assign a variable to a function or method which has the "return type" (Not exactly a type in this case) 'Void', Monkey's compiler won't cause an error. I am using a slightly modified version of V82(A); I basically just added that '_env' fix to my version. That isn't relevant to the problem, though.

The native compiler will obviously catch this, but this is just an odd bug I found with 'trans'.

This can be tested by compiling the following example:

Strict

Public

' Imports:
' Nothing so far.

' Functions:
Function Main:Int()
	' Local variable(s):
	
	' This will not be caught by Monkey's compiler,
	' but the native compiler will technically catch it.
	Local X:= Y()
	
	' You don't even need to use the ':=' operator.
	' As long as you assign it to something, 'trans' won't care.
	Local Z:Void = X
	
	#Rem
		This will cause an internal error in 'trans', though.
		(Uncomment for the compiler's response)
		
		And that's what I expected with the other variables.
	#End
	
	'Local W:Void
	
	' Return the default response.
	Return 0
End

Function Y:Void()
	' This function doesn't actually matter,
	' it's just the return type that's the problem.
	
	Return
End

Nothing too terrible, but it caught me off guard when debugging my own code; I forgot the return type of a specific method, and assumed it wasn't 'Void'.

So, is this an oversight, or is 'Void' just platform-defined to the point of odd behavior like this? Because, just using 'Void' like I did with my 'W' variable will cause an error. But if you assign it, the compiler doesn't care about it being 'Void'.