I don't follow, sorry. How is there terminology changing? Nothing BTW is self explanatory, it's all jargon, and to suggest jargon is self explanatory seems puzzling to me.
Generally methods are viewed as functions that belong to an object (most typically a class instance, though in JavaScript and some other contexts the basic class of "object" can be used generically too. I have yet to see any changing terminology here.
And Iykyk seems a meaningless answer to a question IMHO. If it can't be answered, I guess my point stands, that I really don't know what you're talking about when it comes to changing terminology based on where you invoke something. A method remains a method as far as I know and doesn't change names based on context. Being a subset of functions though, methods are functions, but functions not necessarily methods. And a method can thus be supplied in any context that requires a function.
A method remains a method as far as I know and doesn't change names based on context. Being a subset of functions though, methods are functions, but functions not necessarily methods.
And I was aksing you about:
depending upon where it invooked there technical terminology changes.
To which you responded unhelfully with "Iykyk". I'm curious what terminology changes depending upon where it is invoked here. I'm confident there exists some samples of that, but I can't think of one right now so I was asking you, as you made the claim. And my take is a method is a method is a function that belongs an object, and functions are not all methods?
Not even sure where all that came from. All i did was suggest a more elgenat terser means of writing the draw() method. Take it or leave it. But yhen you responded:
Yes but depending upon where it invooked there technical terminology changes.Thats all. In global level the are similar
which remains a mysterious repsonse to me. Sorry. I'm curious if you have examples of technical terminology changing depending on where it is invoked?
I don't follow, sorry. How is there terminology changing? Nothing BTW is self explanatory, it's all jargon, and to suggest jargon is self explanatory seems puzzling to me.
Generally methods are viewed as functions that belong to an object (most typically a class instance, though in JavaScript and some other contexts the basic class of "object" can be used generically too. I have yet to see any changing terminology here.
And Iykyk seems a meaningless answer to a question IMHO. If it can't be answered, I guess my point stands, that I really don't know what you're talking about when it comes to changing terminology based on where you invoke something. A method remains a method as far as I know and doesn't change names based on context. Being a subset of functions though, methods are functions, but functions not necessarily methods. And a method can thus be supplied in any context that requires a function.
So do you mean that method is function and functions are method both are same thing???
If you read article, its mentioned that
If a member is
If you want to say that method are those functions which we don't declare, then its definitely correct.
I am not getting what else you want to suggest or convey.
I'm confused. Can you read? I wrote:
And I was aksing you about:
To which you responded unhelfully with "Iykyk". I'm curious what terminology changes depending upon where it is invoked here. I'm confident there exists some samples of that, but I can't think of one right now so I was asking you, as you made the claim. And my take is a method is a method is a function that belongs an object, and functions are not all methods?
Not even sure where all that came from. All i did was suggest a more elgenat terser means of writing the
draw()method. Take it or leave it. But yhen you responded:which remains a mysterious repsonse to me. Sorry. I'm curious if you have examples of technical terminology changing depending on where it is invoked?
Okay. There is one more geeky who wants to know this. So, I will extend this blog, so you all get the understanding as well. Okay!!