Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!ihlpf!straka
From: straka@ihlpf.UUCP
Newsgroups: comp.sys.mac
Subject: Re: xbin is great, but it could be even better...
Message-ID: <1391@ihlpf.ATT.COM>
Date: Fri, 10-Apr-87 09:03:41 EST
Article-I.D.: ihlpf.1391
Posted: Fri Apr 10 09:03:41 1987
Date-Received: Sat, 11-Apr-87 18:11:58 EST
References: <1280@midas.TEK.COM>
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 30
Keywords: xbin, suggestions for improvement
Summary: xbin, bhcomb

In article <1280@midas.TEK.COM>, herbw@midas.TEK.COM (Herb Weiner) writes:

> xbin is a marvelous tool.  I have not used BinHex since discovering xbin.
> The following are two suggestions for making xbin even better:

> 2.  Currently, when a program is too big to send as a single posting and must
>     be split, each recipient must manually edit the file to remove the headers.
>     I don't know if it is possible (perhaps an expert could enlighten me), but
>     it would be very nice if xbin could detect "--- End of Part n ---" or some
>     other character (or sequence of characters) which would normally never
>     occur, and suspend the xbin operation until the "---" signifies the next
>     piece.


I have written a little program which does this.  I call it bhcomb.  It
is written in c under Sys V.  It is pretty simple, and works.  Its
capability of traversing files should be incorporated into xbin, but that's
another matter.  I routinely use bhcomb under a simple shell script to
turn multiple binhexed binaries into one file for xbin.

BTW, bhcomb validates BinHex lines as opposed to looking for "--- End of
..." delimeters.

I was going to post this to the net, but it was ~4K, and I posted it
about a month ago.  I'll repost it if I get enough requests.

-- 
Rich Straka     ihnp4!ihlpf!straka

New word for the day: arithmoquinification.  Use it *every* day.