"Craig A. Berry" <[EMAIL PROTECTED]> writes:
> At 07:23 AM 7/25/00 -0400, lane @ DUPHY4.Physics.Drexel.Edu wrote:
>>I haven't heard anything from Charles Bailey recently; last word was that
>>he was going to try the piping code, but working remotely from Texas to
>>his microvax here in Philly is painful, not least because of the slowness
>>of Perl builds on a uV3.
>
> Few things would accelerate the development of Perl on VMS as much as
> someone dredging up a slightly more recent machine for Charles. I assume a
> hobbyist license would be kosher for unremunerated open source development.
I offered him an account on my Alpha; when he's at Penn we're just a
few blocks apart. Hmmmm...I also have a VAXstation 4000 VLC that can
be contributed to the cause.
It's still important to test code on VAXen, and it's getting tough to
find decent fast ones.
> [large snip]
>
>>So I'm pretty confident that (experimentally!) we're AST-safe for VMS 6.2,
>>further confidence can only come from authoritative statements from
>>DEC/Compaq or if someone can dredge through the CRTL source.
>
> Thanks for the careful explanation of where and how the C RTL and ASTs cross
> paths. I agree that the cause for concern is minimal with recent versions
> of the RTL. VMS 5.5 is the unknown, and I think Charles did say recently
> that he wants to continue supporting it. Under 5.5, though, I think disk
> i/o was limited to one thread per process per device unless you installed
> the optional XQP+, so the possibilities of multi-threaded mayhem are quite
> minimal in theory but worth testing if anyone can do so.
Then we *really* need to find some willing volunteer to test under
5.5. I run 6.2 (and will upgrade to 7.2 sometime in the next six
months) and Charles is running 6.2 also. This isn't just a "piping
code" issue; when moving Perl between AXPs and VAXen and between
different VMS versions all kinds of buglets pop up.
--
Drexel University \V --Chuck Lane
======]---------->--------*------------<-------[===========
(215) 895-1545 _/ \ Particle Physics
FAX: (215) 895-5934 /\ /~~~~~~~~~~~ [EMAIL PROTECTED]
