An even BIGGER FYI!!!!
I decided to see if I could use the Project Settings tool to walk the Void-safe setting back down by changing it at load time and doing a clean compile.
I found that if I switched targets I was able to use the Project Settings tool to change the VS settings, and then selected clean compile.
This resulted in the compiler issuing 5 errors (easily corrected). The real issue is: Those 5 errors were not showing up in Transitional, where I was coming from. They did not have anything to do with the Void-safe setting. They were improper creation calls (the code was presuming default_create and the compiler finally caught that there was no default_create, demanding me to choose a creation procedure from the defined choices in the create clause for the failing class creation calls).
So--I correct these errors and decide to up the ante from Conformance to Initialization.
Again--I back out, open ES, use the Project Settings tool to change the VS setting from Conformance to Intialization. I then close the tool, select Clean and Compile and what do I get? 57 (mostly Void-safe) errors that the compiler previously did NOT complain about when the project was previously in VS Initialization mode.
This is really REALLY disappointing. So, I am wondering why I was able to clear all of the compiler errors before--only to return later after clearing all errors in Transitional, going back to Initialization and suddenly I have errors where I had none before?
This tells me that something is perhaps not right in the EIFGENs or perhaps this is just the amazing PAIN of taking a non-void-safe system to void safety???
Oh well -- no more time for this today. Just thought you all would like some FAT to chew!!! :-)
Cheers,
Larry