peraino@gmuvax2.gmu.edu (Bob Peraino) (02/15/91)
>I feel compeled to mention one point that I left out of my immediatly >previous post on this subject: ASC includes a CRC, uuencode does not. On >a machine such as the 48, where incorrect binaries can cause a MEM LOST, . . > ASC will tell you the string is invalid if there is any >coruption; uudecode will not, and could cause problems. uudecode may not have a checksum, but then, why do you really need one, anyway? I don't know about you, but I KERMIT the stuff to my 48, and KERMIT does checksumming anyway, so it can't get from there to here with an error anyway. I suppose, somewhere along the net, something could get hosed, but aren't all those connections checksumming as well? If I'm wrong about this, then indeed, the checksums are important. >James H. Cloos, Jr. Phone: +1 716 673-1250 >cloos@ACSU.Buffalo.EDU Snail: PersonalZipCode: 14048-0772, USA peraino@gmuvax.gmu.edu
cloos@acsu.buffalo.edu (James H. Cloos) (02/15/91)
In article <3475@gmuvax2.gmu.edu> peraino@gmuvax2.gmu.edu (Bob Peraino) writes: | |>I feel compeled to mention one point that I left out of my immediatly |>previous post on this subject: ASC includes a CRC, uuencode does not. On |>a machine such as the 48, where incorrect binaries can cause a MEM LOST, |. |. |> ASC will tell you the string is invalid if there is any |>coruption; uudecode will not, and could cause problems. | | uudecode may not have a checksum, but then, why do you really need |one, anyway? I don't know about you, but I KERMIT the stuff to my |48, and KERMIT does checksumming anyway, so it can't get from there |to here with an error anyway. I suppose, somewhere along the net, |something could get hosed, but aren't all those connections checksumming |as well? If I'm wrong about this, then indeed, the checksums are important. | |>James H. Cloos, Jr. Phone: +1 716 673-1250 |>cloos@ACSU.Buffalo.EDU Snail: PersonalZipCode: 14048-0772, USA | |peraino@gmuvax.gmu.edu I should clarify that this was in responce to putting a UUDECODEr on the 48. In this case the CRC becomes important. If all of the uudecodeing is to be done before transfering to the 48, then the lack of crc is no problem. My conclusion is to post in both forms anything longer than a line or 2. (And those are excluded because I'd just type them in, not trasnfer them over.) -JimC -- James H. Cloos, Jr. Phone: +1 716 673-1250 cloos@ACSU.Buffalo.EDU Snail: PersonalZipCode: 14048-0772, USA cloos@ub.UUCP Quote: <>
TDSTRONG%MTUS5.BITNET@CUNYVM.CUNY.EDU (Tim Strong) (02/17/91)
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 ======================================================================