Subj : Squish __ftsc_date bug
To   : Oli
From : andrew clarke
Date : Wed Feb 10 2021 23:38:16

10 Feb 21 11:04, you wrote to me:

 ac>> I suspect the patch below fixes this, but I've not tested it.

 ac>> It's also necessary to verify it doesn't break when rescanning
 ac>> *.MSG and JAM bases.

 ac>> -    sc_time((union stamp_combo *)&(xmsg.date_written), (char
 ac>> *)msg->datetime); +    strcpy((char *)msg->datetime, (char *)
 ac>> xmsg.__ftsc_date);

 Ol> What happens if xmsg.__ftsc_date is empty? Local messages don't have an
 Ol> __ftsc_date and it could also be missing for other reasons (messages
 Ol> converted from another message base format, copied/moved in a message
 Ol> editor or tossed by a tosser that doesn't copy the __ftsc_date).

Good point. But it's easy to test for that condition.

if (*xmsg.__ftsc_date == '\0')
{
    /* __ftsc_date is empty, so use xmsg.date_written */
    sc_time( ...
}
else
{
    /* use xmsg.__ftsc_date */
    strcpy( ...
}

--- GoldED+/BSD 1.1.5-b20180707
 * Origin: Blizzard of Ozz, Melbourne, Victoria, Australia (3:633/267)

.