TIP: Click on subject to list as thread! ANSI
echo: aust_c_here
to: Paul Edwards
from: Michael Stapleton
date: 1995-10-29 03:36:00
subject: Re: FREQing

-=> On 10-23-95  23:06 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 .

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

PE> If you have been unsuccessful, but done most of the legwork, do
PE> you want to post it here and I'll see if I can see any obvious
PE> problems (e.g. spelling "Dialer" as "Dialler").

Yes, thanks. I'll put it into this packet. I tried to retain the
original form as much as possible, so it shouldn't be too hard to
read, especially if you have any experience with REXX.

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

MS> I'm impressed! For a lot of people, portability just means that

PE> Thank you!  The bulk of stuff that I write will work on any ISO
PE> conforming compiler.  That includes my mailprocessor, Tobruk.

Does this mean I can run a point, using code that compiles on my
Amiga? That's great! (But I'll try to get Devil working first.)

MS> their code compiles on different Intel-based environments. :(

PE> When I'm writing a program on an Intel machine, I think of 
PE> IBM C/370 V2.0 for MVS mainframes.  When I'm writing on the 
PE> MVS mainframe, I think of Borland C++ 3.1 for MSDOS.

The first machine that I ever used was an IBM 360/20 in the old
Museum of Applied Arts & Sciences, in Ultimo, back in 1973.  I
learnt PL/I on this beastie, as well as IBM 360 assembler & machine
code.  I can still even remember some opcodes (Branch 47xx, Halt 99)
from when I did a little hand-assembling.

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

PE> That's interesting.  When I actually went to compile MD5, I found
PE> a couple of problems, which I fixed, and are included in the latest
PE> OZPD (can't remember when I made the change), but anyway, the 
PE> latest version of OZPD is OZPD9510.ZIP, available for FREQ as
PE> "OZPD" from 3:711/934.  I would be interested in any changes you
PE> needed to make for the Amiga.

I didn't actually change anything, but I did need to create a
config.h file from scratch.  I also created a test program, which
prints the name & digest of all files named in the command line.
This is useful to search for duplicate files.

PE> I'd also be interested if you actually understood the algorithm,

Yeah, sure! :) I think I understannd the general principles, though.

PE> and could take out any dependency on longs being exactly
PE> 32-bits.  A few & 0xFFFFFFFFUL should fix that problem, but
PE> someone actually needs to take the time to read the code to know
PE> where to put them.

The code isn't that long.  :) I think that it might only require
masking in byteReverse(), but I'll have a closer look soon.  OTOH,
it might be better to get someone with a 64 bit environment to work
on this.  :)

Michael Stapleton of Graphic Bits.

 * AmyBW v2.10 *
... This tagline is encrypted
--- Blue Wave/RA v2.10 AmyBW
* Origin: The Three Amigas - better than two (3:713/615.0)
SEEN-BY: 50/99 620/243 623/630 711/401 409 410 413 430 510 807 808 809 932
SEEN-BY: 711/934 712/508 515 713/111 317 601 611 615 618 700 826 888 914
SEEN-BY: 714/906 800/1 7877/2809
@PATH: 713/615 888 711/808 809 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.