I generally define shared variables as Public as opposed to passing them via byVal or byRef. Most commonly, I call a subroutine or function to establish a value for said variable, making it usable anywhere in my script. Will someone please explain to me the benefit of using byVal/byRef vs simply creating a Public var?
-
If you would like to post, please check out the MrExcel Message Board FAQ and register here. If you forgot your password, you can reset your password.
shg
MrExcel MVP
- Joined
- May 7, 2008
- Messages
- 21,841
- Office Version
- 2010
- Platform
- Windows
The notions are kind of perpendicular. Passing ByVal gives the called routine a copy of the variable (a copy of the pointer for object variables), which prevents the called procedure from changing them as they can with variables passed ByRef.
Making a variable Public just increases its visibility to all procedures in a project that don't have a variable of the same name declared more locally.
Public variables have their place, but they are generally less used than abused, and make code less atomic / reusable, and more difficult to debug.
Making a variable Public just increases its visibility to all procedures in a project that don't have a variable of the same name declared more locally.
Public variables have their place, but they are generally less used than abused, and make code less atomic / reusable, and more difficult to debug.
Upvote
0
