> Hi Greg,
>
> Noted. Yes, I do agree that our docs could do with some cleanup. If you
have
> any suggestions, feel free to send them to me, and I'll look at getting
them
> fixed in the next rev.
>
> Rgds,
> Jun-Kiat Lam
> Metrowerks Technical Support
>
Here are a few documentation suggestions.
1. In _Targeting_Palm_OS_, in the section
"Large Application Projects for Palm OS", there
is no mention of the need to turn off "Link Single
Segment" in the Link Settings. This is discussed
elsewhere, but imperfect people (like me) often
fail to read the entire manual before doing
something. There should be a complete list
of what needs to be done to create a large
application, even though there is a separate
linker discussion elsewhere.
2. This suggestion is unfortunately vague, but
maybe you or someone else will be able to
think of specifics. There are places in the docs
where I'm sometimes uncertain whether all
68K processors are being discussed, or whether
only MacOS 68K processors are relevant.
I understand that CodeWarrior has a history that
predates the Palm, so you really can't be blamed
for this situation. But when we encounter a 68K
reference in the docs, it would nice if we knew for
sure if it applied to the Palm or not.
3. FileOpen() doc: I have had the experience of
failing to open a file, but FileOpen() still returned
a non-zero value. It is necessary to for the programmer
to check the *errP argument.
4. StrNCat(): the documentation already says that
this differs from the standard C strncat() function,
but this should be in BOLD print so that dopey people
like me will notice it the first time they read it. This is
a Palm Computing doc issue.
5. FileTell(): unlike ftell(), this can tell us the size
of the file as well as the current file cursor location.
Perhaps there should be an entry for stat() in the
index that points to FileTell(). Of course, there are
still differences, such as the need for a file to be
open for FileTell() to work, but such differences
could be in BOLD print.. This is a Palm Computing
doc issue.
6. This is a Palm Computing issue, not a Metrowerks
issue. I consider the MemoPad demo to be part of
the documentation. The weird error messages in
phase 21 of MemoPad need to be explained and
or fixed.
Thanks,
Greg Bungo
[EMAIL PROTECTED]
(630)949-3250 voice
(630)949-3299 fax
