"Michael Needlman" <[EMAIL PROTECTED]> wrote in message
news:8038@palm-dev-forum...
> I mean, they're simply not there. The values are "undefined in context" in
> the debugger, and referencing them in the code causes run-time errors, as
in
> referencing unallocated memory.
In other words, if you try to dereference the other pointer arguments, you
get run-time errors?
> I have been programming professionally for 27 years <snip>
Sorry to "quote the book" at you. It's not always clear whether the obvious
needs to be stated.
> Please refer to my original msg to see, verbatim, my declaration.
Here it is again:
[function prototype]
Int CompareOrders(OrderRec *rec1, OrderRec *rec2, Int other,
SortRecordInfoPtr rec1SortInfo, SortRecordInfoPtr re2SortInfo, VoidHand
appInfoH)
[calling code]
DmQuickSort(gOrdersDB, (DmComparF*)CompareOrders, 0);
You're passing in 0 for "other", so you should expect CompareOrders to be
passed 0 for "other". You should expect "appInfoH" to be a valid handle
containing gOrdersDB's app info block, unless it doesn't have one. You
should expect the two record info pointers to point to valid memory
containing the record attributes (including category) and unique ID.
I wonder if you've discovered a bug. Are rec1SortInfo and rec2SortInfo
always invalid (ie. can't be dereferenced)? Or are they usually valid, but
not always?
--
Danny Epstein
OS Engineer, Palm Inc.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
