PE>> The *.MSG header has no place in it for "date
arrived". It could
PE>> be kludged on though, but just isn't.
PE> Ok, I tell a lie. What has actually happened is that there are two
PE> different standards for *.MSG.
MS> How convenient. :)
PE> The one documented in FTS-1 is what I referenced when writing
PE> Tobruk, which doesn't have the date arrived in it. The one that
PE> is used in Msged is the one that does have the date arrived. I
PE> will need to convert both Msged and Tobruk to use the same
PE> format. So hang on to your hat on that one!
MS> Righto.
I have done the mods to both MSGED and Tobruk to handle date arrived. I
don't think I should send you the changes though, because that will just
confuse your code with mine. BTW, did you get the message I wrote to you
in PUBLIC_DOMAIN about the Lattice makefile? Also, I think Andrew is
likely to be merging all the changes in to MSGED over Christmas. Can you
get your mods in to him soon? Especially the non-Lattice-5.1 mods. I'm
not sure what the philosophy on the Lattice 5.1 mods should be. I think
you should have an independent archive containing 5.1 fixups, which can be
used in all products expecting an ISO environment etc. Then again, I
included a PACIFIC.C in MSGED last time. But then I also made available a
patch to Pacific C's header files as a separate thing. The thing is, it's
likely to be me, not you, that will be doing the Amiga compile, since I
have the more advanced compiler. So it's only people who are stuck with an
old Lattice compiler and want to do development that need the fixups. I
think I'd start with a separate Lattice C thing. BTW, in order to get
quick.c to compile, you must have done something to make up for the fact
that fstat() isn't defined. What did you do? I hope you created a LATTICE
etc instead of using SASC, because the current SASC has an fstat().
BTW, the message in PUBLIC_DOMAIN was trying to get a Lattice C makefile as
just one file, instead of needing the separate link file.
BFN. Paul.
@EOT:
---
* Origin: X (3:711/934.9)
|