You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When defining a new UDF on 32bit, the Localname can be any friendlyname. However - on 64BIT, the local name has to be the same as the entrypoint. I can actually make the entrypoint whatever I want, and the function will still work. It seems the 64BIT is using the LOCAL name to search for the function in the library.
The text was updated successfully, but these errors were encountered:
Agreed, more details/example is required. We have not found any issues with the use or declaration of UDF between 32 and 64bit versions. The semantic rules for the definitions are exact the same.
Submitted by: Claudius (pikfrik)
When defining a new UDF on 32bit, the Localname can be any friendlyname. However - on 64BIT, the local name has to be the same as the entrypoint. I can actually make the entrypoint whatever I want, and the function will still work. It seems the 64BIT is using the LOCAL name to search for the function in the library.
The text was updated successfully, but these errors were encountered: