Subj : not ignoring you... but...
To   : Bj”rn Felten
From : mark lewis
Date : Sun Jul 11 2004 03:09 pm

 SL>> Despite a bugfix on this very subject from 1.02 to 1.03,

 BF>    Those all seems to be fixed in the 1.05 version I have. I
 BF> also have 1.06, but that one is always 'unable to open
 BF> messagebase' for some reason that I haven't bothered to look
 BF> for.

its not anything in the 1.06 code as i use it here as designed... in fact, my 
stuff even goes so far as to create the necessary directories and files if they 
don't exist ;)

 SL>> Change
 SL>> If JM^.TxtSubChars <= TxtSubBufSize Then
 SL>> Into
 SL>> If JM^.TxtSubChars <= TxtSubBufSize-1 Then

 BF>    Hmmm... Why not just delete the '=' sign? :)

haha... that would have worked, too... but its not necessary that i've been 
able to tell...

 BF>    There are some bugs in MkMsgCvt, that I've tracked down to
 BF> the JAM part, since all works fine to and fro any combination

msgcvt was just something tossed together to show using the message libraries 
as a blackbox... the problem isn't in mkmsgcvt but in the library or the 
compiler...

 BF> of msg-bases, just not from MSG to JAM. After a couple of
 BF> hundred msgs (different on different "folders", but always on
 BF> the same msg (usually, but not always, some big msg) in the
 BF> same folder, the program crashes with a run-time error 216.

216? that's not even listed in my TP6 reference stuff... are you sure about 
that? i just looked...

[time passes]

ahh... just looked in BP7 and see that that's a GPF... hummm... sounds like an 
errant pointer trying to access memory outside its allocation...

 BF> Going MSG->Squish->JAM works. Really strange bug. Plus of
 BF> course the S-B lines are added to the msg-text -- might be a
 BF> correlated bug, but since it seems to be impossible to do any
 BF> serious debugging on the package, it's hard to find the bug.

paths should done be using the dokludgeln when writting them to the base... 
seenbys should be done using dokludgeln, too, but they are not...

ie: hacked together, untested... possibly add to dokludgeln section...

  Else If Copy(Str,1,7) = 'SEEN-BY' Then
    Begin
    TmpStr := StripLead(Copy(Str,8,255),':');
    TmpStr := StripBoth(TmpStr,' ');
    AddSubField(2001, TmpStr);
    End

and i see what appears to be an error in MsgStartUp (for reading JAM bases) in 
that seenbys are prefixed with a ^A when they shouldn't be... at least, not if 
they are going into PKT files... in any case, in JAM bases, seenbys are code 
2001 as shown in the above modified snippet from dokludgeln... doing the 
seenbys properly needs to be built in the same manner as doing the path line 
except without the leading ^A character...


hummm... guess i'll have to dig in and write some JAM reading code...

what's wierd is that JAM is apparently the only message base format that takes 
special care with control lines... to all the others, its simply a string of 
text...

its been a long while since i've dug into this stuff ;)

)\/(ark

 
* Origin: (1:3634/12)

.