🚀 go-pugleaf

-----BEGIN PGP SIGNED MESSAGE-----

\n";
 
   SISS sincerely hopes noone was positioned to monitor this Internet
   traffic, because they would have picked up the full transfer.
 
*******************************************************************************
*******************************************************************************
*******************************************************************************
 
    There are plenty of alternatives to
 
        a) sending our proprietary code over the unprotected Internet
        b) disclosing our code to a third party
 
    The answer to a) is: don't do it. Get MD/SOO permission to use a courier.
 
    The answer to b) is:
 
        o Isolated the bug(s) to the smallest amount necessary to reproduce
          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 produc


-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.5.5

5Ug8eb5qw5df7HWdxH6KCiWefUt4OLb5Z1PyJARbcvM/DJHCrHnmqB08qnP6aelK
rmbKWCLLB2NZ8gJjGxXsygN+OoavyRB6YVNKSyrDvpM1Ko279o+YbEj45ZZh+VuP
5lznkfE6i0Dm3iIbX8U8YudkJYnTRw4gtJj8mH0bf9JK+TQQwt565Zy/6rBxHqa0
QOWBctVzWyEMTjCAuqjLTAEtexrWUNB5jCKZzUCD2I1hKB==
=5EBQ
-----END PGP SIGNATURE-----