problems with conflicting function names

[Manao]

What happens with user defined function:

function mpeg2dec_motionmask (.......){} ?

They create an error, and I don't see a problem here. The user can define it another way.

Nobody knows about all exported functions from all installed plugins.

Yes, but an error message saying function's name is already in use should be enough.

I'll never prefer that quadro point thing, one point is enough

Yes, of course, but '.' is already in use ( clip.filter() ), so you have to find another separator.

BTW, banning '_' from dll & function name would resolve almost all the issues you're expecting. The filters using '_' in the dll name or a function name can be counted on the finger of one hand ( I know only _2DcleanerYUY2 )

[stickboy]

Originally posted by Manao

They create an error, and I don't see a problem here.

If I'm understanding sh0dan correctly, there would be no error.

Despite what the AviSynth docs say, user-defined functions seem to override plug-ins and built-in function names. (I think it's better that way. Functions in the script itself should take precedence. It would be bad if adding a plug-in to the autoload directory broke an existing script.) Nothing should happen to that user-defined function.

The current approach is that when a plug-in adds its function names to the namespace, AviSynth generates the corresponding dll_ names and adds those to the namespace too. This has the advantage of not requiring any changes to the parser and not having any ambiguity, but it has the disadvantage that the generated names won't necessarily be unique. If there is a collision, behavior would be the same as it currently is.

BTW, banning '_' from dll & function name would resolve almost all the issues you're expecting. The filters using '_' in the dll name or a function name can be counted on the finger of one hand ( I know only _2DcleanerYUY2 )

If you want to include user-defined functions, I can think of quite a number of functions that have underscores in their names.

[zettai]

If we are creating alias function names do we really need overrides at all?

Is it not possible that when a filter is parsed that the regular function names are defined AND an alias name which is filtername_functionname is also defined. If a name exists then only the latter is defined.

This not only allows you to use the first funciton in the chain as Function() but it also allows you to specify which type you use whether there is a function clash or not.

So even if I didn't have any other filters that contained Telecide I could still have a script containing decomb511_telecide(order=1) and know what I was going to get and if by chance I happen to leave an old version in the plugin dir I'd still be able to use the new one.

Am I making any sense?

[stickboy]

Originally posted by zettai
Is it not possible that when a filter is parsed that the regular function names are defined AND an alias name which is filtername_functionname is also defined.

I think this is what the new scheme already does.

If a name exists then only the latter is defined.

This not only allows you to use the first funciton in the chain as Function() but it also allows you to specify which type you use whether there is a function clash or not.

Currently whatever plug-in was loaded last will take Function(). Last or first seems pretty arbitrary to me; I don't see why there should be any major reason to prefer one over the other, so it might as well be last. (If we include user-defined functions in our discussion, then having the last definition override the earlier ones makes more sense.)

So even if I didn't have any other filters that contained Telecide I could still have a script containing decomb511_telecide(order=1) and know what I was going to get and if by chance I happen to leave an old version in the plugin dir I'd still be able to use the new one.

I imagine that this is what the new scheme already does.

[WarpEnterprises]

Originally posted by stickboy
Despite what the AviSynth docs say, user-defined functions seem to override plug-ins and built-in function names.

You are right - shame on me

[stickboy]

Hmm... I'm trying the 2004-03-14 AviSynth build, and it looks like the new DLLName_function() support works only for auto-loaded plug-ins. It doesn't seem to auto-generate the additional names for plug-ins loaded from LoadPlugin.

Is this the intended behavior?

[stickboy]

Also, do the built-in functions get additional names too?