Skip to content

VoltScript

ForAll Loops and Type Mismatches

There are always challenges when moving from something familiar to something similar but different. When you've been working with that "something familiar" for a very long time, some things become second nature. But when you move to "something similar but different", sooner or later you hit an error and become convinced it's not working like it used to. This is even more probable if enhancements mean you more frequently come across a specific paradigm. The rash developer starts throwing accusations, assuming they must be right because they have years of experience on their side. The wise developer double-checks first...and may find out that they were mistaken.

Reaping the Benefits of Standard

More than three years ago we began work on VoltScript. A little over a year ago we released our first Early Access code drop. There were certain core principles to which we developed. Two of these were a modern developer experience and adoption of standard development practices.

Over recent weeks I received ample evidence of the benefits as I improved and extended Archipelago, the build management engine of VoltScript.

LotusScript Classes - Singleton Addendum

After my blog post last week on LotusScript classes and using Static Property Get to create singletons, there was some discussion on OpenNTF's Discord about the challenges of forcing use of the singleton. "Singleton" is a misnomer really, because it's not scoped to the JVM asaJava singleton would be. But I can't think of a better name yet, so I'll stick with that terminology, but be aware of the specific scope for static instances in LotusScript / VoltScript.