[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | Alpha Migration Tools - Digital Confidential |
| Notice: | Kits: VEST v1.1A: Note 15.60, mx v1.2-4: Notes 4.23 & 4.24 |
| Moderator: | TALLIS::GORTON |
|
| Created: | Wed Jun 13 1990 |
| Last Modified: | Mon May 26 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 970 |
| Total number of notes: | 4239 |
968.0. "White paper for customer on developing common source for VAX & Alpha" by NNTPD::"[email protected]" (Russell GRAHAM) Fri May 16 1997 04:12
Hi,
I am looking for a white paper, article, etc that explains why it is better,
when developing an application for both VAX and ALpha (OpenVMS) with a single
set of source code, to choose the Alpha as the main development and test
platform. Then to do some testing on the VAX pre release.
It is possible if developing on the VAX to "get lazy" and code VAX specific
programs, designs, etc, which will then break on the Alpha.
By using the Alpha as the main platform, coding & design have to be done
correctly to work at all. Such programs will have a better chance of working
subsequently on the VAX.
etc ....
We have a customer who is moving from VAX to Alpha with this issue as a
consideration.
I was hoping to get some literature to support the arguement that they should
primarily use Alpha.
Any ideas?
Regards,
Russell Graham
NSIS, Sydney
@SNO
Thanks,
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 968.1 | | HYDRA::SCHAFER | Mark Schafer, SPE MRO | Tue May 20 1997 10:58 | 8 |
| Lazy programmers won't get better just by working on a specific
platform! You might suggest that they set up a VAX and an Alpha to
share the code base and build both nightly. Reviewing the build logs
should reveal "compatibility" problems. Also suggest they read
"Migrating an Application from OpenVMS VAX to OpenVMS Alpha" and decide
for themselves.
http://www.openvms.digital.com:81/ssb71/6459/6459P.HTM
|