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
I find myself avoiding early-bound references where possible, mainly because of their version instability. Is this something others would be interested in?
We'd be talking about references other than VBE7.dll, Excel.exe, stdole2.tlb, MSO.dll, FM20.dll ofc
E.G. If a library requires an early-bound reference to Scripting.Dictionary and VBScript.Regexp then we'd have the following:
*[🖼][p_win][⭐️][a_all][🔗](#"Scripting.Dictionary;VBScript.Regexp") SomeVBALibrary - Does something
However libraries which create Late-bound objects like:
setrx=CreateObject("VBScript.Regexp")
wouldn't have to include the emoji
The text was updated successfully, but these errors were encountered:
Do you have a specific example? I understand the hesitation around early-bound references, but perhaps adding the emoji or not is something to consider at a later stage? Not least because it's going to require a whole lot of thinking and work on my part when submitting links for inclusion to the list! 😄
but perhaps adding the emoji or not is something to consider at a later stage?
Yes, agreed. I'd suggest we look at automating the process for the links we have already, but do so at a later stage when the list is more established 😊
I find myself avoiding early-bound references where possible, mainly because of their version instability. Is this something others would be interested in?
We'd be talking about references other than VBE7.dll, Excel.exe, stdole2.tlb, MSO.dll, FM20.dll ofc
E.G. If a library requires an early-bound reference to Scripting.Dictionary and VBScript.Regexp then we'd have the following:
However libraries which create Late-bound objects like:
wouldn't have to include the emoji
The text was updated successfully, but these errors were encountered: