the error. According to the previous email traffic between these
two people, there were two compile-time bugs. The programmer can
be faulted for not using two orders of magnitude fewer lines for
demonstrating the error. A small fragment of code can be emailed.
o If the problem is compile-time, email the relevant C/C++
preprocessor output snippet. The comments by the programmer in the
email transfer state THE CODE DOESN'T COMPILE ANYWAY.
o Have the vendor deliver a "debug" version of their product. That
would be a good use for email. Sun Microsystems does that with a
C++ product for us, their customer. Email the results back.
o Have the vendor visit to troubleshoot.
o Requested a login via SecureID and Salomon's netblazer, supporting
28.8 PPP (TCP/IP for windowing connectivity) for the vendor. Let
them transfer in any tools they need to troubleshoot.
Short-term access.
o If it is truly necessary to transfer a large amount of code, such as
Informix working to convert a large Sybase app, then take the time
to write a shell script that (using say 'sed') scrambles the names
of environment variables, and be sure to hand-ruin any proprietary
algorithms.
Why is transfer of Salomon proprietary source to a vendor's site the last
step to try? Because Salomon loses co
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 2.4.1
NyeXf4aT8qMyKCCB9+v6xUpG9Jk52r4BK4gckhIhufmCWJ81ozY4NGvHuYqhlD8y
4tsFBGZc7xQsMKTD4ZK3Wz3OQ4RL+1upWTkD8AFt48sgv5DNRCz6zja8AiuRjAaH
z44OZjVUIY9goSO0ce4bLQV/xEVUY4W3V+je8V1NToDiqk3+EBS7ViAjPJUrf2pt
/5Reane+e78HpnlfVDCvKp2h5z==
=K1eh
-----END PGP SIGNATURE-----