Peter wrote:
> >An impressively small patch. It looks good.
Thanks. It would have been a good bit smaller except for the following hardware model
on the testdrive system:
$ write sys$output f$getsyi("HW_MODEL")
0
and, since we had been assuming anything with HW_MODEL <= 1024 was a
VAX, caused the configuration process to think the Itanium was a VAX.
I assume they just haven't finished filling out the internal table or
whatever SYS$GETSYI uses to know system specifics.
A couple of other changes were necessitated by the fact that the
compiler now identifies itself as "hp C" rather than "DEC C" or
"Compaq C" so I had to add checks for that. This is something we'd
have had to do for Alpha and VAX anyway.
> >By the way pod/perlport.pod (er, I mean [.POD]PERLPORT.POD;1 of course :-)
>>mentions the "VMS_VAX" vs. "VMS_AXP" archname strings and might be
> >in need of some modification to incorporate the new port to "VMS_IA64".
Yes, there are certainly documentation changes that will need to be
made. I just wanted to get something quick and dirty out there that
would possibly make it into 5.8.3 and provide something for early
adopters to adopt.
And then Willem said:
>IMHO VMS_I64 is better: again, 3 characters. I think HP uses the same:
>
>VAX - AXP - I64
>
>VAX - ALPHA - IA64
Yes, I wondered about that. I went with IA64 because that's what
f$getsyi("ARCH_NAME") returns, but then we don't follow that on
Alpha, where it just returns "Alpha" but we use "AXP". Consider the
exact choice of letters subject to change, and I should have said
that the initial support of the I-thing by whatever name is as
experimental and subject to change as early adopter's kit itself.
--
________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
