-=> On 10-07-95  23:49 you wrote to me <=-

Hi Paul,

PE> No, but inside DEVIL261 you will find a file called SIMPLE.SLT
PE> which is VERY VERY simple, and you should be able to convert
PE> this into a script for .

I suppose that it's simple if you're used to C-like macro languages.
:) I've attempted to convert this to a Term ARexx script, as I
mentioned on your board.

MS> I usually use Term, but it is a little ungainly, so I sometimes
MS> use NComm ...  not that any of these names would mean much to
MS> you.  :)

PE> You might be surprised.  If you FREQ TFON*.* from 3:711/934, you
PE> will get TFON710.ZIP, which has a file in it called tfon.c,
PE> which has things like this in it...

PE> #if defined(MSDOS)
PE> #define TFVERS "710"
PE> #define TFDATE "September 1995"
PE> #define NAME "tfon"
PE> #elif defined(AMIGA)
PE> #define TFVERS "110"
PE> #define TFDATE "September 1995"
PE> #define NAME "nfon"
PE> #else
PE> #error you must define MSDOS or AMIGA
PE> #endif

PE> #elif defined(AMIGA)
PE> /* V1.9 ncomm file format */
PE> static struct pb_Data
PE> {

PE> etc

PE> It's been a long time since I tested it on the Amiga though.

I'm impressed! For a lot of people, portability just means that their
code compiles on different Intel-based environments. :(

FWIW, I prefer to put most portability stuff in .h files to keep the
main source less cluttered. I did this to the MD5 code you posted
here recently when I "Amigatized" it.

Michael Stapleton of Graphic Bits.

 * AmyBW v2.10 *
... This tagline is encrypted
--- Blue Wave/RA v2.10 AmyBW