Tue 2002-11-19 04:24, andrew clarke (3:633/267) wrote to All:

 > If you reply to a message, Msged (or SMAPI, I'm not sure yet) will
 > alter the date of the message you're replying to, I'm assuming
 > because it thinks it's not "correct". It really shouldn't be doing
 > this!

In hindsight, Msged has to alter the header of the message you're replying
to in order to add the new message to its reply chain.  But why was the
xmsg.__ftsc_date field rewritten?

Ah!  In SquishWriteXmsg() (sq_write.c):

    if (xmsg.date_written.date.yr > 19 || xmsg.__ftsc_date[0] == 0)
    {
        MsgCvtFTSCDateToBinary((char *) xmsg.__ftsc_date,
          (union stamp_combo *) &xmsg.date_written
        );
    }

Why is this here?!  xmsg.__ftsc_date should only be stored when a message
is tossed!  The above code is in direct contrast to the comments in
msgapi.h:

typedef struct _xmsg
{
...
    byte __ftsc_date[20];       /* Obsolete date information.  If it weren't
                                 * for the fact that FTSC standards say that
                                 * one cannot modify an in-transit message,
                                 * I'd be VERY tempted to axe this field
                                 * entirely, and recreate an FTSC-compatible
                                 * date field using the information in
                                 * 'date_written' upon export.  Nobody should
                                 * use this field, except possibly for tossers
                                 * and scanners.  All others should use one
                                 * of the two binary datestamps, above. */
}
XMSG;

Regards
Andrew

-- mail{at}ozzmosis.com

--- Msged/NT 6.1.1