something like this:
macro blah:int()
local n:int (local names would require additional symbols to avoid conflicts - actually, i dont know how this would be solved)
.....
.....
return n
endmacro
id like to see this feature - treating it like a function in every
way..but a statement like:
local x:int=blah()
would result in the following code being generated at
compile time:
local n:int
.....
.....
x=n (were return is mapped to initial assignment)
Well id like to see it anyway :]
- its not massively important, but might help speedup
some routines..though to be honest i dont know if bmax
already determines whether functions/methods are expanded
or called based on context...i wouldnt think it attempts
to optimise in this kind of way..but i jst dont know..
anyhoO.. thats what i want :] :p ;]
macro blah:int()
local n:int (local names would require additional symbols to avoid conflicts - actually, i dont know how this would be solved)
.....
.....
return n
endmacro
id like to see this feature - treating it like a function in every
way..but a statement like:
local x:int=blah()
would result in the following code being generated at
compile time:
local n:int
.....
.....
x=n (were return is mapped to initial assignment)
Well id like to see it anyway :]
- its not massively important, but might help speedup
some routines..though to be honest i dont know if bmax
already determines whether functions/methods are expanded
or called based on context...i wouldnt think it attempts
to optimise in this kind of way..but i jst dont know..
anyhoO.. thats what i want :] :p ;]