VBA Rubberducking

12:00 AM

RELOAD!

All you need to specify is whether a declaration of the type is a result and what the result description string should look like

Duga

[Minesweeper] Games Played: 79, Bombs Used: 31, Moves Performed: 11077, New Users: 6

IvenBach

@M.Doerner github.com/IvenBach/Rubberduck/blob/… is what actually handles all the logic?

M.Doerner

Yep, that handels the base logic.

IvenBach

Ok. That is a clearer.

I was still on the wrong path of implementing InspectionBase.DoGetInpsectionResults from my first attempt.

IvenBach

12:53 AM

hrm... I'm back to not being able to differentiate between a class module and doc object.

M.Doerner

8:39 AM

I see the ways to do that:

Via Declaration.GetModuleParent(declaration).DeclarationType or via declaration.QualifiedModuleName.ComponentType.

Quack Exchange

11:29 AM

0

Q: How can I speed up my VBA code?

I want to ask for help on how to further accelerate this code. Operation of the code: It copies 1-1 worksheets from 3 different workbooks to 3 worksheets of the new workbook. Inserts, copies, and formats different columns. Then, by examining different criteria on a worksheet called "lista", type ...

Duga

2:06 PM

[rubberduck-vba/Rubberduck] Irubataru opened issue #5637: Function calls and the DefaultMemberRequired inspection

> I have a question that's probably very subjective, but maybe the VBA veterans here know something I do not.

Because of my background primarily from C++ I have a need to distinguish between a member function call and a member variable access when using a class. So just for the sake of having an example, say I have a class `MyClass`

```vb
Private Type Members
Foo As String
Bar As String
End Type

Private this As Members

Public Function IsEmpty() As Boolean

IsEmpty = _

[rubberduck-vba/Rubberduck] Irubataru added label support to issue #5637: Function calls and the DefaultMemberRequired inspection

Duga

2:18 PM

[rubberduck-vba/Rubberduck] Irubataru created comment on issue #5637: Function calls and the DefaultMemberRequired inspection

> An additional observation.

I always thought the reason I got this inspection was because the expression `MyObject.IsEmpty()` would be evaluated as `(MyObject.IsEmpty)()` and that it would do a spurious function call on the return value, but that doesn't seem to be the case. If I add another class to my project, let's call it `DebuggingDefaultCaller` and have the following class contents

```vb
'Class: DebuggingDefaultCaller

'@DefaultMember
Public Sub PrintHello()
Debug.Print "He

[rubberduck-vba/Rubberduck] Irubataru edited comment on issue #5637: Function calls and the DefaultMemberRequired inspection

> An additional observation.

I always thought the reason I got this inspection was because the expression `MyObject.IsEmpty()` would be evaluated as `(MyObject.IsEmpty)()` and that it would do a spurious function call on the return value, but that doesn't seem to be the case. If I add another class to my project, let's call it `DebuggingDefaultCaller` and have the following class contents

```vb
'Class: DebuggingDefaultCaller

'@DefaultMember
Public Sub PrintHello()
Debug.Print "He

[rubberduck-vba/Rubberduck] Irubataru edited comment on issue #5637: Function calls and the DefaultMemberRequired inspection

> An additional observation.

I always thought the reason I got this inspection was because the expression `MyObject.IsEmpty()` would be evaluated as `(MyObject.IsEmpty)()` and that it would do a spurious function call on the return value, but that doesn't seem to be the case. If I add another class to my project, let's call it `DebuggingDefaultCaller` and have the following class contents

```vb
'Class: DebuggingDefaultCaller

'@DefaultMember
Public Sub PrintHello()
Debug.Print "He

Duga

2:39 PM

[rubberduck-vba/Rubberduck] bclothier created comment on issue #5637: Function calls and the DefaultMemberRequired inspection

> Can you confirm if you’re using the latest pre-release. There is a similar issue that was addressed in this PR

[rubberduck-vba/Rubberduck] SteveLaycock created comment on issue #5637: Function calls and the DefaultMemberRequired inspection

> > Personally I think there is value in having the parentheses there because at least if used consistently it informs me when reading the code that the value is a computed value of the class and not something more inherent to the object which is how I see Properties.

This only works because you are aware of the internals of a Class/Object. The whole point of an object is that you don't need to (shouldn't) know what goes on inside the Class/Object when you access a property. Consequently yo

Quack Exchange

0

Q: Fast Native Memory Manipulation in VBA

I've been quite annoyed lately by the fact that the CopyMemory API (RtlMoveMemory on Windows and MemMove on Mac) is running much slower than it used to, on certain computers. For example on one of my machines (x64 Windows and x32 Office) the CopyMemory API is running about 600 times slower than a...

vba memory-management pointers

Duga

3:20 PM

[rubberduck-vba/Rubberduck] Irubataru created comment on issue #5637: Function calls and the DefaultMemberRequired inspection

> >
>
> Can you confirm if you’re using the latest pre-release. There is a [similar issue](https://github.com/rubberduck-vba/Rubberduck/issues/5581) that was addressed in [this PR](https://github.com/rubberduck-vba/Rubberduck/pull/5597)

I wasn't using the latest pre-release, I was on `2.5.1.5557`, you are right, with the newest pre-release the issue goes away. On my main project I still have 250 of them, some of which doesn't seem like they should trigger, but I'll look at them more close

[rubberduck-vba/Rubberduck] Irubataru created comment on issue #5637: Function calls and the DefaultMemberRequired inspection

> >
>
> > Personally I think there is value in having the parentheses there because at least if used consistently it informs me when reading the code that the value is a computed value of the class and not something more inherent to the object which is how I see Properties.
>
> This only works because you are aware of the internals of a Class/Object. The whole point of an object is that you don't need to (shouldn't) know what goes on inside the Class/Object when you access a property. Con

[rubberduck-vba/Rubberduck] Irubataru closed issue #5637: Function calls and the DefaultMemberRequired inspection

IvenBach

4:46 PM

@M.Doerner :+1: QualifiedModuleName.ComponentType was what I needed.

IvenBach

8:04 PM

Make it work) Went directly into calling mocks. Felt messy.
Make it right) Kept reviewing inheritance on other tests. Refactored to use higher abstraction.

@Vogel612 do you have any experience with -multiinst files being created when using Notepad++ as the git editor?

I needed to RTM to ignore specific files locally.

Vogel612

9:41 PM

@IvenBach nope, but I recall something about notepad++ being problematic as an editor because it doesn't necessarily exit-code the invocation if you create a commit...

which kind of deadlocks git

IvenBach

exit-code the invocation?

IE it considers you're in a persistent "writing a commit message" state?

Vogel612

that's what I had happen to me

only if np++ had other editors open, though

basically git waits for a 0 exit code on the editor it calls for the file with the commit message in it

IvenBach

10:04 PM

Hrm... I get the behavior when I have np++ open and git commit it'll open a new tab, but git immediately considers the tab to have been closed with no commit message.

IIRC I installed it with -multiinst flag enabled.

I been too lazy to properly fix it and just work around it.

Vogel612

@IvenBach that's because np++ has a global lock and you didn't open another instance

so calling the binary just gives the path to the file to the running np++ instance and then terminates

which is why git considers it closed

(because it gets an exit code)

IvenBach

10:19 PM

hrm... A result for the inspection being found. Why is that?

It displays in the settings window. Has a severity and CodeInspectionType

IvenBach