Talk:User defined script functions

From Avisynth

I do not like the term "script function". Internal function is script function too. I prefer "user defined function" (or "User function" or "user script function") Fizick 17:02, 1 September 2007 (PDT)

I guess that depends on how we define a "script function" right? I don't see an internal filter as a script function, but i can understand that people do. What about "user defined script function"? Wilbert 04:57, 2 September 2007 (PDT)

What about simply "function"? After all there aren't any other kind of functions in the language.Gzarkadas 12:41, 2 September 2007 (PDT)

I say about user defined functions (macros-functions?). There are also built-in functions, and some functions in plugins. IMO we should preserve some old terms. "user defined script function" is better. But we must be more clear.

Current text says, that "filter" has input and output as a clip, but "function" returns not a clip (numeric, string). But user-defined script "function" may be a "filter" (with input and output clip), may be numeric fuction, etc. This is a little confusing. IMO "function" is more wide verb than "filter" both in general and in Avisynth. I.e. "filter" is kind of "function" if input and output are clips. So, it make filtration of input video clip. It result is not a clip, it is not a filter (but some function). If there is no input clip, it is not a filter too. Avisource is not a filter. It is source function.

Second. IMO, "non-clip" functions was correct name. Why revise it? More correct name for current "Internal function" is "Internal non-clip functions". (numeric, string, etc) Fizick 14:01, 2 September 2007 (PDT)