At this point I have to disagree, I like where the PDK is headed and I'll be completely pleased when they work out a couple of bugs. I purchased the PDK solely for the purpose of creating ActiveX controls with PerlCtrl, currently my money has not been well spent.

There is an issue in the Win32::OLE module that ships with AS 5.8, or more simply the module isn't 5.8 thread safe. Since PerlCtrl is tightly intertwined with Win32::OLE I find it disappointing that they shipped their 5.0 SDK without resolving that issue prior.

The problem comes when a Win32::OLE object is created in one thread, then during the cloning stage when spawning a second thread yields a corrupted copy, and explicitly calling share() on the object prior to spawning corrupts both copies. I've submitted this bug to AS and hopefully will see a resolution soon so that I may proceed with my projects.

Another issue I've run into isn't a fault of the PDK but uncovers a bug in Win32::GUI when used with a PerlCtrl object. The issue there is that Win32::GUI doesn't properly track the current Perl interpreter which causes error when creating a window from a .dll that has been created by a VB application.

Once these issues are resolved I will be happy as a clam. :)

-Nitrox