Version 2.1 is out, and includes significant new logic for MACRO support, as well as debugging the conversion process.
In particular, we wanted to make it easier for people to scan a subject SAS program for compatibility problems with Carolina. And if a conversion broke, we wanted Carolina to point to the location where it broke. These two features were hotly, if politely, sought by our new alliance partner IBM. Hope they help.
Version 2.1 is out, and includes significant new logic for MACRO support, as well as debugging the conversion process.
(*apologies to the Coen Brothers)
We've been making the rounds of a few major Fortune 50-scale customers, and most people want to initiate their evaluation of Carolina.
I thought I would briefly describe how I recommend we get this done.
First a couple of ideas that frame the action: