Rick,
>Just lack of time; to tweak settings,fix up outdated calls, etc.
>It took me only 20 minutes to track down all of the stuff needed
>to get TxtPrepFindString to work under release 1 of Codewarrier
>for Pilots. (And it was a little more complicated than usual, because
>of the funny international trapjump thingee)
>
>To compare, I tried seeing if I could convert
>the OS 3.0 ToDo example to OS3.1 in 20 minutes or less.
>I couldn't. Multiple compiler errors complaining about ...
>ChrIsHardKey() -- obsolete
>IsPrint() --
>sizeofchar
>GetCharAttr
>IsAlpha
>IsSpace
>charAttrP = GetCharAttr();
>IsAlNum
All of these calls are now obsolete. The ChrIsHardKey() macro should be
replaced by TxtCharisHardKey(), the IsXXXX macros should be replaced by
TxtCharIsXXX macros, the sizeofchar macro should be replaced by
sizeOf7BitChar, and the GetCharAttr() routine shouldn't be used at all.
>All complaints about undefined calls, or something like that.
>And no obvious explanation of where to find the equivalent
>replacements, or what the missing header might be. (except
>for the useful compiler error about ChrIsHardKey being
>replace by a Txt routine.
>I know you have to be free to change old calls to make way
>for the new. For me, though, it's not worth the time to
>go through and try to find out how to change old working
>code to jump through the hoops of the new stuff.
1. The headers are being modified to generate useful compiler errors for
all of these obsolete routines.
2. The easy "fix" to get everything to compile is to #define
NON_INTERNATIONAL before including any headers...so I'd put this in a
prefix header. This will re-enable all of the obsoleted routines. The
downside is that you'll be using macros, trap calls, and what not that
guarantee your code will not work on devices with character encodings other
than Latin.
>If you are asking for recommendations for future releases of CW,
>I think that many of us that have substantial amounts of working
>code based heavily on your example projects would benefit from
>an idiot-level summary of things to change to accomodate the
>new definitions. Basically, a prominent document titled "How
>to change the old Example projects to compile without errors
>under this version of CW". (I know there is usually somthing
>similar in the final releases, but it isn't usually geared
>to the old projects, per se)
Sounds like a good idea to me.
-- Ken
Ken Krugler
TransPac Software, Inc.
<http://www.transpac.com>
+1 530-470-9200 (direct) +1 408-261-7550 (main)
