🚀 go-pugleaf

In article <Bvo7FC.M01@ithaca.com>, garry@ithaca.com (Garry Wiegand) writes:
>The Big 3 that come to mind:
>
>3. Shareable image version numbers should go away.

>The primary purpose in life of #3, the shareable image version
>numbers, is to guard to the transfer table against "accidents". Once
>the transfer table is gone (#2) one can immediately do away with the
>version numbers (or change the default setting to "match any".)
>You'll recall that version-number unpleasantness on Vaxcrtl.exe is
>what got us started on this thread originally.

Er, just how do you think you'll do this?  What the fuck's supposed to happen
when an image has a call to someplace in never-never-land (something that's
guaranteed to happen when an image linked against a later shareable image,
using a new routine, is run against an old one?

Forget your simplistic arm-waving.  Tell us, oh genius, in detailed terms,
exactly how you plan to  avoid this sort of problem.   In other words, jackass: 
PUT UP OR SHUT UP!  I'd be willing to bet you $100 against your $1 that you
can't do it.  C'mon, put your money where your mouth is.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.