Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Carefully Consider Use of (Default) ByRef vs (Explicit) ByVal #47

Open
GCuser99 opened this issue Jan 1, 2022 · 1 comment
Open

Carefully Consider Use of (Default) ByRef vs (Explicit) ByVal #47

GCuser99 opened this issue Jan 1, 2022 · 1 comment

Comments

@GCuser99
Copy link

GCuser99 commented Jan 1, 2022

I went through the entire code base and changed any input parameter that was not typed as Object or Variant (such as strongly-typed Double, Long, Boolean, or String) to an explicit ByVal. Sorry I should have mentioned this before because some of my proposed modifications will throw an error if not.

@ghost
Copy link

ghost commented Jan 2, 2022

Thank You!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant