* Forwarded (from: jamnntpd) by mark lewis using timEd/2 1.10.y2k+.
* Originally from Scott Street (1:266/420.1) to Björn Felten.
* Original dated: Thu Jun 28 2012, 13:30
On 6/27/2012 5:12 PM, Bj”rn Felten -> Scott Street wrote:
SS>> I've just pulled the win32 zip off the website until I
SS>> can track down the issue.
BF> Ahhh... Just as I put in my Billings folder here. I'll pull if off
BF> too, then.
SS>> Look for a new version, perhaps tomorrow.
Well, last night, I did two things.
First, I too the original 1.0 source (non-smapi) and got it to compile in
Visual C++ 2010 Express. Which, was easier then trying to get my MIGW32 to
build it. Then I cleaned up the code to reduce the warnings to VCE complaining
only about using stricmp - some warning about being insecure?!? - added that to
my to-do list.
Secondly, I merged my SSL and performance improvements into the original code
base. I also cleaned up unused local variables. I am currently testing the
build on my point (posted this message with it) as well as having my automated
testing scripts hammer my poor Windows VM for all its worth! :)
BF> No hurry, mate! We've been waiting for years for something to happen
BF> here, and you certainly are a breeze of fresh air in those dusty
BF> chambers of ours. :)
Yeah, but I feel I got everyone's hopes up... I hate to disappoint.
BF> Not that I'm all that interested in the MSG format, but Squish might
BF> have been interesting eight years ago (I've used SquishMail on 2:203/0
BF> for more than a decade and half or so, so I already had most of the
BF> echoes in SQM format). Not any more, really, though...
After reading this is when I decided that the bloat of supporting all those
different message bases, when only JAM is actually useful to me (and it seems
others) did I backtrack to the non-smapi version.
___
- Origin: -=[ SSAlpha da'Point/win32 ]=- (1:266/420.1)
[/END of FORWARD]
)\/(ark
* Origin: (1:3634/12)
|