by Unlicensed Unknown user
The first betas of Clarion 10 are now in the hands of participating third party folks and other developers.
...
The look and feel of the IDE is pretty much the same as it is for Clarion 9. Here's a comparison, with C9 above and C10 below.
New files
One of the first things I do with any new Clarion release is compare the install files with those from the previous release.
...
Presumably this is the log viewer mentioned in the release notes. The log viewer is a handy utility that can help you find the location of GPFs in your code. For instance, I induced a null reference GPF in the JSON example app, saved the GPF info to a log file, then opened the GPF log in the viewer (from the Tools menu).
If you've compiled in debug mode then what you'll see is pretty much the same as you'd get if you were running your app using the debug version of ClaRUN.dll.
...
That tells me that the GPF has something to do with the JSONDataClass's ClearObject method, and the calling code is in TakeEvent, which is a big step toward finding the cause of my GPF.
bin\awssdk.dll
LibSrc\win\ClaAwsS3.clw
LibSrc\win\ClaAwsS3.inc
These files are for Amazon S3 support, and awssdk.dll is the Amazon Web Services SDK DLL. It's also a .NET DLL, which pretty strongly suggests that Clarion's new support for Amazon S3 comes via some interop. It also suggests that if you want to use the S3 support your customers will need .NET 3.5 installed.
...