I have it working with Build 629.
On 21-Jan-02 Tim Bunce wrote: > On Mon, Jan 21, 2002 at 09:27:29AM +0100, [EMAIL PROTECTED] wrote: >> On 20 Jan 2002, at 21:47, Tim Bunce wrote: >> >> > On Tue, Jan 15, 2002 at 09:51:28AM +0000, Simon Oliver wrote: >> > > Beware if runing ActiveState perl. ActivePerl is compiled with >> > > iThreads, which is not compatible with Storable >> > >> > Why not? >> > Does the author know? >> > Do p5p and/or ActiveState know? >> > Is the problem being worked on by anyone? >> > >> > Tim. >> >> This is copied'n'pasted from the release notes of the current ActivePerl >> build: >> >> The fork() emulation has known limitations. See perlfork for a detailed summary. In >particular, >> fork() emulation will not work correctly with extensions that are either not >thread-safe, or maintain >> internal state that cannot be cloned in the psuedo-child process. This caveat >currently applies to >> extensions such as Tk and Storable. >> >> I don't know if the above can lead to basic restrictions in the usage of >> DBD::ProxyServer by design, but I know from own experience, that there has >> been at least one ActivePerl release (Perl 5.6.0, build 622) where Storable >> crashed upon errors when retrieve()ing or thaw()ing in eval blocks (="pseudo- >> child-processes" ?). Perhaps opinions about ActivePerl and Storable are >> triggered by this and probably other broken ActivePerl releases. The current >> release (631) does not exhibit this problem. > > Are you saying that DBD::ProxyServer works with release 631? > > Tim. ---------------------------------- E-Mail: Scott T. Hildreth <[EMAIL PROTECTED]> Date: 21-Jan-02 Time: 08:16:00 ----------------------------------
