Rubberduck VS stdVBA

But, with the RubberduckVBA plugin, the editor certainly becomes very usable.

I agree - it generally looks pretty clean in general. Do you use Rubberduck? If not, I'd run the Code Inspections - it will always find some best practices that you missed and you can tweak the output to your preference.

I suppose this is like the opposite of this project: https://rubberduckvba.com

This project is extending the VB6 IDE?

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).

Honestly, this is something I've been wanting to do for a while... Last I looked though, I couldn't find many good resources on how WASI (or the byte code) worked... And VBA being single threaded might make things difficult too...

I have already built my own code interpreter in VBA to make Lambda syntax possible: https://github.com/sancarn/stdVBA/blob/master/src/stdLambda.... so I know it's definitely possible, just haven't figured out WASM yet...

I do RPA from VBA personally using IAccessiblity. See stdAcc (https://github.com/sancarn/stdVBA/blob/master/src/stdAcc.cls) and an example (https://github.com/sancarn/stdVBA-examples/tree/main/Example...)

I have invested copious amounts of time into building VBA libraries (https://github.com/sancarn/stdVBA) and as much as I love vba there are some highly limiting actual problems with VBA (https://sancarn.github.io/vba-articles/issues-with-vba.html) which really hurt the language. But yes a large portion of the hate VBA gets is from the state of VBA projects (https://sancarn.github.io/vba-articles/why-is-vba-most-dread...)

I have an open source compiler-interpreter for VBA here: https://github.com/sancarn/stdVBA/blob/master/src/stdLambda....

In case you were interested :P

You could have just treated everything as variant correct? That's what we do here: https://github.com/sancarn/stdVBA/blob/master/src/stdLambda....

Sometimes, though more of a library / tool developer here. See stdVBA or stdVBA-examples

Otherwise this library poses as an example of how to use stdVBA libraries. Libraries used in this project: stdEnumerator, stdArray, stdCallback, stdCOM, stdICallable, stdLambda, stdRegex.

If you want a solution though see stdSettings. There are both system and user settings. Users are bound by their domain, so should work across organisations :)

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.