Hello Rich!

22 Nov 16 08:09, you wrote to me:

 RL> I'm sticking to 2.x but I'll check it out and may get some insight on
 RL> how to do some things.

Yeah.. I don't use 3.x either... I really don't understand the reason for the
breakage casued in the 3.x branch... I know some stuff I do, would need
rewritten as would stuff I use that need the same, and for some of that its
abandonware so...

 RL> on the documentation. I read the JAM stuff and my mind melts. I just
 RL> can't wrap my head around binary file manipulation... yet! Never give
 RL> up! Never Surrender!

Well I avoided a lot of things, succesfully for a LONG time.. C and Python
being two of them...

Python came back as for some stuff I do on Pi's its a must

C was a forced thing for a more recent issue... now its sort of a mission for
something...


 RL> Yes I do. I'm trying to code a CNet BBS clone in Python and make it
 RL> more modern on the backend. I figured JAM would be easy for fido/FTN

Well hopefully the one helps, its 2.x...

I know I would love to have a python Jam lib so I could test some ideas... but
the posted JHR reader might just be the test suite I need.. since thats really
all I need to read anyway, at least in theory.


 RL> OK, good to know! Thank you!

This came up else where with some stuff that is written for a tosser and
NNTP/Fido server all by the same author..

The issue is variable size at least from what I can see right now... I don't
know if there is a way to typedef ulong to be unsigned 32bit interger v. it
defaulting to 64b when compiled on a 64b systems or not.. forcing gcc to 32b
mode seems to resolve it.. but I just have a bug about doing that... I would
rather have a 64b binary, that uses 32b variables....

Is there no longer a "C" echo????? Didn't see one in the list I have, but maybe
 its not exhaustive???


Rick


... Ding Dong the Witch is DEAD! I Made America Great Again! President Trump!
--- GoldED+/LNX 1.1.5-b20160322
 * Origin: Vina's Talos Moon Base Alpha (1:135/377)