mailing binary files

[Marc Espie]

In article <16968 at crdgw1.crd.ge.com> volpe at camelback.crd.ge.com (Christopher R Volpe) writes:
>In article <1025 at tfsg.UUCP>, mark at tfsg.UUCP (Mark Crafts) writes:
>|>Quick question:
>|>
>|>What's the best way to send binary files through E-mail (you know, with
>|>a "---cut here---" line) so that when "cut there", it can be saved to
>|>a file and executed (or unpacked then executed or whatever).
>
>Well, C doesn't have any built-in "mail binary file" operator, so we'll
>have to fudge it. 
[much deleted]
>I would have, but seeing how this is just so applicable to comp.lang.c, I
>thought I'd post it.         
>==================
>Chris Volpe
>G.E. Corporate R&D
>volpecr at crd.ge.com

So what's wrong with uuencode/uudecode ?
I don't know of any reasonable machine which doesn't support it
(AMIGA/UNIX/PC/MAC). It does precisely what you want in a standard
and reasonably efficient way... you may even build a better interface
on top of it (like a filter which scans uuencoded message, pass them
through, creating decoded files automatically. I have such a filter
on a permanent basis in my terminal emulator setting... which does
only support 7bits ascii.)
(I know this does not precisely belong in comp.lang.c, except
that folks were starting to spout code redesigning the wheel.)

You can program what you want, but you will gain some time if
you use the uuencoded files standard. Better still ! There's a
good chance you can *use* code written by other people :-).
--
    Marc (espie at flamingo.stanford.edu)
So many FORTRAN programmers, so little time...