Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!shelby!msi.umn.edu!noc.MR.NET!gacvx2.gac.edu!hhdist
From: TDSTRONG%MTUS5.BITNET@CUNYVM.CUNY.EDU (Tim Strong)
Newsgroups: comp.sys.handhelds
Subject: RE: ASC versus uuencode
Message-ID: <679A891440002A3F@gacvx2.gac.edu>
Date: 17 Feb 91 04:36:30 GMT
Lines: 16
Return-path: <@CUNYVM.CUNY.EDU:TDSTRONG@MTUS5.BITNET>
In-reply-to: Your message of Thu, 14 Feb 1991 23:38 CST
To: handhelds@gac.edu

Incidentally, some one recently said something to the effect ..'why
did Bill use an obsure code he made up himself to encode the objects
anyway..'  Or something like that.  ASC-> isn't some obscure code.  Look
at the headers.  ASC-> produces a string of hexadecimal characters that
represent the hexadecimal numbers that go into the binary image of the object
in memory.  What you are looking at is virtually binary dump.  That also makes
ASC-> very useful for learning the headers and structure of object in memory.

Just another little reason for ASC-> and ->ASC.

======================================================================
  ___
  :__)  _   _:  _   _   Tim Strong <tdstrong%mtus5.bitnet@cunyvm.edu>
  :  \ (_: (_: (_: :    Michigan Tech.    Houghton, Michigan

======================================================================