Bug? Sub parameter name named as a custom type compiles fine on B4A but fails on B4i

Alessandro71

Well-Known Member
Licensed User
Longtime User
I know this is a bad practice, but I'm writing just because it does not generate any warning until compile time.
Just by error I created a custom type with the same name of a parameter of a Sub in the same Code module.
B4A compiles without error, while B4i fails at compilation time with an error.
 
Cookies are required to use this site. You must accept them to continue using the site. Learn more…