naming_conflicts
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | naming_conflicts [2018/02/18 05:53] (current) – created wolfgangriedmann | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Naming conflicts ====== | ||
+ | |||
+ | Unfortunately, | ||
+ | |||
+ | * No class in your application can have the same name as your application itself. So if your application (exe or dll) is has a name of MyClass, you cannot have a class MyClass in your application. If you cannot change the name of your class, change the name of your application to app.MyClass or something similar | ||
+ | * your application cannot have the same name as any of the VO runtime methods. Otherwise you will have to call the function fully qualified: | ||
+ | < | ||
+ | The relative error is | ||
+ | < | ||
+ | * you cannot have a method and a access/ | ||
+ | * The Vulcan compiler has not problem when two functions of the same name exists in different assemblies: it takes one of them, and you cannot define which. The X# compiler is more precise and does not allow this. | ||
naming_conflicts.txt · Last modified: 2018/02/18 05:53 by wolfgangriedmann