Well I dont think it should be removed.
Self in a function does at present, and still should in future represent the type name when called from an function.
That is
Should be the same as
That is the way Bmax uses Self IS BETTER than "This" and only ppl who think it should work like "This" consider it a Bug.
I see no reason at all why it should be changed
Fair enough there might be a good reason for it not to be the way it is. But if the only reason is "It wasnt supposed to work like that", then that isnt a good enough reason
Self in a function does at present, and still should in future represent the type name when called from an function.
That is
Function MemberofAType() self.AGlobalMember EndFunction
Should be the same as
Function MemberofAType() AType.AGlobalMember EndFunction
That is the way Bmax uses Self IS BETTER than "This" and only ppl who think it should work like "This" consider it a Bug.
I see no reason at all why it should be changed
unless you have different scopes with the same, then use Typename.Functionname) if you don't want to rewrite your code in the future
But why change self at all, if all its going to mean, is that some people are going to have to change there code?Fair enough there might be a good reason for it not to be the way it is. But if the only reason is "It wasnt supposed to work like that", then that isnt a good enough reason