[comp.sys.atari.st] Ian Lepore: e-mail address ?

L.B.Brown@newcastle.ac.uk (L.B. Brown) (06/25/91)

Hi,

I need to know Ian Lepore's (author of the Gemfast AES and VDI bindings)
e-mail address so I can bring to his attention some small bugs I have
found. I can't find one in the gemfast V1.5 documentation. Does he have
an e-mail address? Does anyone know how to contact him?

Any help would be most appreciated.

Leigh.


	Leigh Brown.	UK   : L.B.Brown@uk.ac.newcastle
			World: L.B.Brown@newcastle.ac.uk

steve@thelake.mn.org (Steve Yelvington) (06/26/91)

[In article <1991Jun25.111424.27940@newcastle.ac.uk>,
     L.B.Brown@newcastle.ac.uk (L.B. Brown) writes ... ]

 > I need to know Ian Lepore's (author of the Gemfast AES and VDI bindings)
 > e-mail address so I can bring to his attention some small bugs I have
 > found. I can't find one in the gemfast V1.5 documentation. Does he have
 > an e-mail address? Does anyone know how to contact him?

Ian doesn't seem to have an Internet address, and mail sent to the Citadel
BBS in Denver that he used to call has not been answered.

However, Mike Dorman, the person from whom I obtained GEMFAST 1.5, seems
to have a channel to him (perhaps through BIX). If you'll send the report
to me I'll try to have it forwarded to Ian via Mike.

(Oh, by the way, I now have the MadMac source code for GEMFAST 1.5, and
I'll mail it off to atari.archive sometime soon.)

Here's a note from Ian that was reposted on GEnie.

|Category 3,  Topic 23
|Message 13        Mon Jun 24, 1991
|M.DORMAN2 [Mike Dorman]      at 22:24 EDT
| 
|The official word from Ian Lepore:
|
| GemFast is one of the few things I'm willing to put a lot of support effort
|into.  If folks want to pass bug descriptions along to me, I'll do my best to
|fix them.  I don't require source code fixes.  GemFast is a strange and
|convoluted critter internally, it'd be unfair of me to ask other folks to wade
|through it and find my bugs.  If they can't give a good description of the
|bug, I'm willing to accept their executable file and a description of how to
|navigate my way in their program to the point where the bug happens.  I have
|good tools for logging what the AES and GemFast are doing internally, so I may
|be in a better position to debug than they are.
|
| The first thing to ask folks when they mention a GemFast bug is: what version
|are you using?  If not v1.5, all bets are off, I *know* there's bugs in
|earlier versions. :-)  I don't guarantee 2-day turnaround on bugfixes or
|anything, but I can often find a workaround real quickly, and if it's a major
|bug, I start thinking about a new release.  (Speaking of which, I've been
|thinking of v1.6 for a while now anyway, I have no bug reports in yet, but I
|do have some outstanding requests for new functions.  Now would be the time
|get those bug reports in...)
|
| In fact, a new GemFast release is the next thing on my to-do list after I
|finish the 'heat-and-serve' release of Sozobon, which ought to be within a
|week or so.  (That's what I said a week ago, however!)


I don't know what he means by heat-and-serve Sozobon C, but it does sound
interesting, doesn't it?

 ----
 Steve Yelvington
 steve@thelake.mn.org