stdVBA VS Rubberduck

Typically I use my stdEnumerator and stdLambda class for this:

Aha motivations for stdVBA which is a library I made. It resolves some of these points in some ways. E.G. stdLambda acts as a Lambda syntax for VBA. stdCallback allows you to ripe the benefits of first class functions, without those functions existing.

my own stdVBA and some examples at stdVBA-UI

As you can see sometimes these techniques can get rather complicated, however in reality most of the complexities of this task can be hidden behind an abstraction. This is where I suggest the use of the stdVBA library. This library (created by myself) contains some simple abstractions of the IAccessible API and work in conjunction with stdLambda to help you create small utilities like the above, with very little effort:

Uses stdVBA's stdAcc library, but works a charm! :D

You'd need to download stdLambda, stdEnumerator and stdICallable and import these into your VBA library in order to work with them.

There're numerous unit testors out there already. I do find it interesting as to why many prefer this result.equalTo(3) compared to result = 3. My own is a single class and goes down the Test.Assert message, x=y route. As a result most of my tests look like:

Yes, i created it as part of stdVBA

For sharepoint you need to use SOAP. I've got a small example here

At that point, I decided to try the fabulous stdLambda tool, developed by u/sancarn. I found that stdLambda correctly evaluated all the corner cases that made Volpi's class fail. This fact excited me, so I decided to measure the time it took to evaluate an expression with variables, noticing that the u/sancarn library was quite efficient. At that point, I started to measure the performance by evaluating functions like sin, cos, tan, abs, the results seemed strange to me when I noticed that the performance was almost 50 times lower when compared to the results obtained when measuring the performance by evaluating expressions without calls to built-in functions.

A lot of Runescape resource to XP / hours calculators. What they really need to do is replace VBA with a proper programming interface. Rubberduck VBA [1] Adds some essential features into the VBA IDE but they really just need to add C# support directly.

[1]: https://rubberduckvba.com/

Also if you are doing VBA go and take a look at https://rubberduckvba.com/

If anyone out there is unfortunate to have to be working with VBA in the VBE, please check out https://rubberduckvba.com/

I forgot. If you work with VBA look at this https://rubberduckvba.com/ It basically replaces the VBA dev environment with something that in many ways is better than VS Code.

The SQLiteC subpackage uses custom compiled x32 and x64 SQLite binaries for Windows, with all extensions, including ICU, enabled (included in the repository). The SQLiteODBC driver is the other dependency (its bitness must match that of the used Excel version, and it must be installed on the target machine) used by the SQLiteADO subpackage. This project unit testing relies on the RubberDuck VBA framework. Because of early bindings, this add-in must also be installed (it does not require admin privileges).

try https://github.com/rubberduck-vba/Rubberduck/issues

Oh, and if you're going to do software engineering in VBA, you must use the open siurce Rubberduck VBA plug-in. It makes the VBE usable. https://rubberduckvba.com/

I tried searching everywhere, aparently i needed to do a "part-parse" according to this thread: https://github.com/rubberduck-vba/Rubberduck/issues/3081 However that didnt solve anything.