Path: utzoo!attcan!uunet!husc6!think!ames!mailrus!tut.cis.ohio-state.edu!ukma!psuvm.bitnet!cunyvm!ndsuvm1!ndsuvax!ncreed
From: ncreed@ndsuvax.UUCP (W. Reed)
Newsgroups: comp.sys.amiga
Subject: Re: Unlock?   AarRgh!
Summary: Net Humor (originaly in .tech)
Message-ID: <1833@ndsuvax.UUCP>
Date: 23 Nov 88 18:04:28 GMT
References: <2174@kalliope.rice.edu>
Reply-To: ncreed@ndsuvax.UUCP (W. Reed)
Organization: North Dakota State University, Fargo
Lines: 21


In article <2174@kalliope.rice.edu> phil@rice.edu (William LeFebvre) writes:
>Now I thought I had this all figured out.  The capitalization rule for the
>library routine names seemed very simple:  the first letter in every word
>or word-abbreviation is capitalized.  Thus: CreateDir, AllocMem,
>PrintIText (the I being short for "Intui" or "Intuition").  Well, imagine
>my surprise when the linker told me last night that the reference "Unlock"
>was not resolved.  Turns out I wanted "UnLock".  So Commodore, what's "Un"
>short for?  "Undo"?  "Unallocate"?  "Unotbeneedingthisanymore"?

Well, I'm not commodore, but I have it from Reliable sources that the
Un in UnLock is short for under.  What happens is this:
    UnLock goes "Under" the Lock you wish to remove, and installs a
    little virus-like explosive software bomb.  (Sorry I can't
    go into much more detail, but I signed a non-disclosure
    agreement on the details of the implementation.)  UnLock
    then blows the Lock all to hell!

Hope this helps explain things...

--
------  Walter Reed  ------   + uunet!ndsuvax!ncreed or ncreed@ndsuvax.BITNET
"There's no point in being    +      or ncreed@plains.NoDak.edu
 grown up if you can't be     +
 childish sometimes!" Dr. Who + USnAIL: 925 9th Ave W.  West Fargo, ND 58078