Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!bloom-beacon!snorkelwacker!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!kuhub.cc.ukans.edu!anu-news!list
From: munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston)
Newsgroups: news.software.anu-news
Subject: RE: rot13 utility in DCL.  a PIG, but it works....
Message-ID: <8912200842.AA22375@uunet.uu.net>
Date: 21 Dec 89 00:32:53 GMT
Sender: ANU-NEWS Discussion <ANU-NEWS@NDSUVM1.BITNET>
Reply-To: Geoff Huston <munnari!csc.anu.oz.au!gih900@UUNET.UU.NET>
Lines: 28

>Well, after I asked for it, I got a few copies of a nice rot-13 utility
>(one in fortran, the other in "C").
>
>However, I don't have any "real" compilers on my system (we're a big
>MUMPS shop...), so I decided to see if I could do it in DCL.   Heh. :-)
>
>Well, I've always been under the impression that a creative person can
>do ANYTHING in DCL, if one tries hard enough.
>
>45 minutes later, I completed the following sketchy utility.
>
>It works great.  If you do not answer a name for 'Output file', sys$output
>is assumed.
     
I'm impressed!!!
     
>god, I must be nuts.
I think the same of myself all too often!
     
>(geoff, as a suggestion, add a "POST/ROT13" qualifier.   You already have
>READ/ROT13, so it shouldn't be TOO tough....)
     
Wouldn't it be better to have a TPU edit procedure called rot13 to allow you
to rot the necessary bits??
     
(said he trying to avoid having to add the code)
     
Geoff