stop warring.
It's all about context. I understand what Mark meant in that context. There's no point mega deconstructing it, wait until Mark gets up again (he's probably asleep right now.)
********
However, I think that, within a type, a Function and a sub-function should *NOT* be treated the same. Sure you shouldn't be able to call a method from a Type's Function because self doesn't exist, unless you do AType.Method() of course. HOWEVER, if a sub-function is inside a method, treating it like a normal type function totally limits it's usefulness as an inlining tool. It's already inside a method, so banning the sub-function from calling other methods where self is implicit seems unneccessary. I hope that as a result of this finding the langauge can be expanded not limited :-)
********
I'll post the same in the other thread.
It's all about context. I understand what Mark meant in that context. There's no point mega deconstructing it, wait until Mark gets up again (he's probably asleep right now.)
********
However, I think that, within a type, a Function and a sub-function should *NOT* be treated the same. Sure you shouldn't be able to call a method from a Type's Function because self doesn't exist, unless you do AType.Method() of course. HOWEVER, if a sub-function is inside a method, treating it like a normal type function totally limits it's usefulness as an inlining tool. It's already inside a method, so banning the sub-function from calling other methods where self is implicit seems unneccessary. I hope that as a result of this finding the langauge can be expanded not limited :-)
********
I'll post the same in the other thread.