Hi Hanz,
I'll try to answer your question:
CA-VO is coming from Clipper, in MS-DOS times one of the most used
programming languages for business software.
The architects of VO (short for Visual Objects) took several ideas from
Clipper, like codeblocks, arrays and the garbage collector combined
with the internal macro compiler and ported them to the Windows
platform, initially Win16 (Windows 3.1), and then Win32 (starting with
Windows 95).
Personally, I'm working with VO since it is available, and IMHO it is
still the most productive development platform you can find for the
Win32 platform.
On the one side, you have high level libraries like the GUI, the RDD
and the SQL classes, combined with potent string and array functions,
codeblocks and a very clean language.
On the other side, you can go down like with C and make manual memory
allocations, pointer aritmetics and other low level functions.
The main problem of VO now is the problem of the platform itself: Win32
has its age, and will be replaced sometimes by the .NET platform.
Therefore GrafX, the distributor of VO, has created a new product,
Vulcan.NET, that is highly compatible to VO, and now another company
has plans to launch another compatible product, XSharp (that currently
is in development). Vulcan.NET actually ships in version 4.
VO applications are rock solid, as is the development environment. One
of the revolutions of VO (unfortunately missing in Vulcan.NET and
XSharp) is the repository and the entity based compile process.
If you have other questions, please ask.
HTH
Wolfgang
--