Newsgroups: comp.lang.apl
Path: watmath!watserv1!utgpu!news-server.csri.toronto.edu!torsqnt!jtsv16!itcyyz!yrloc!rbe
From: rbe@yrloc.ipsa.reuter.COM (Robert Bernecky)
Subject: Re: Programming in J
Message-ID: <1991Nov23.163542.12840@yrloc.ipsa.reuter.COM>
Reply-To: rbe@yrloc.ipsa.reuter.COM (Robert Bernecky)
Organization: Snake Island Research Inc, Toronto
References: <1991Nov14.204636.11703feustel@netcom.COM> <1991Nov19.011150.29495@yrloc.ipsa.reuter.COM> <1991Nov19.211311.27484feustel@netcom.COM> <1991Nov20.055922.22395@apollo.hp.com> <1991Nov20.183040.7209feustel@netcom.COM>
Date: Sat, 23 Nov 91 16:35:42 GMT

In article <1991Nov20.183040.7209feustel@netcom.COM> feustel@netcom.COM (David Feustel) writes:
>The problem with not having an internal crc is that different people
>will have different crcs and also that you can't use a crc to check code
>being typed in that doesn't have a crc printed with it.

Well, one simple approach to use is the following:

a. Write the CRC function of your choice. This is a good exercise in
   APL or J anyway.

b. Include the CRC function with your postings.

c. Include the result of applying the CRC to the "relevant part" of
   your posting as part of the posting. Perhaps even apply th CRC to
   itself? 

Bob






Robert Bernecky      rbe@yrloc.ipsa.reuter.com  bernecky@itrchq.itrc.on.ca 
Snake Island Research Inc  (416) 368-6944   FAX: (416) 360-4694 
18 Fifth Street, Ward's Island
Toronto, Ontario M5J 2B9 
Canada
