| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re^2: dates |
Wed 2002-11-20 09:53, Stas Degteff (2:5080/102) wrote to andrew clarke:
>>> This is not need: XMSG used as message buffer and only elements of
>>> this structure read/write.
ac>> No, there's more to it than that!
ac>> XMSG is also used as a parameter to MsgWriteMsg(). If an application
ac>> program thinks sizeof(XMSG) == 248, and the precompiled SMAPI
ac>> library thinks sizeof(XMSG) == 238, you will have CORRUPT DATA (as I
ac>> demonstrated).
ac>> Also, in msgapi.h there is:
ac>> #define XMSG_FROM_SIZE 36
ac>> #define XMSG_TO_SIZE 36
ac>> #define XMSG_SUBJ_SIZE 72
ac>> #define XMSG_SIZE (94 + XMSG_FROM_SIZE + XMSG_TO_SIZE +
ac>> XMSG_SUBJ_SIZE)
> This define is incorrect. For XMSG size must be use sizeof(XMSG)...
Then why is it there?
Do you understand the problem I'm talking about AT ALL?
-- mail{at}ozzmosis.com
--- Msged/NT 6.1.1
* Origin: Blizzard of Ozz, Mt Eliza, Victoria, Australia (3:633/267)SEEN-BY: 633/270 @PATH: 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.