XCMD Limitations
Ben Rubinstein
benr at cogapp.com
Thu Oct 24 07:42:01 EDT 2002
on 23/10/02 11:46 pm, Richard Gaskin wrote
> Perhaps it could be rewritten in native MetaTalk....
I wasn't clear enough, sorry. The stack uses about 25 XFCN/XCMDs. I'm sure
that I can recode all of them in native MetaTalk except this one. This one
has to be in C. It uses proprietary libraries and custom code which has to
be shared with some other apps to guarantee accuracy. Recoding in another
language is not an option, even if time was not a factor.
I've negotiated an allocation of a limited time to demonstrate that the
system can succesfully be transitioned to MC/Rev; otherwise it's going to go
elsewhere. I can recode the other externals in native MetaTalk, and if we
get to continue down this path I will, for speed and cleanliness; but if I
can't get the whole thing working quite quickly, that path will be capped.
But in any case this function is core to the whole project, so I have to get
it reliably working.
I have the source code, so if I know what the problem areas are I expect I
can code round them (it doesn't need to interact with the host in any very
interesting ways). I've already fixed one crash by re-implementing
StrToRect. The problem is I need to know the full set of unsupported calls
- I can't afford to just fix the ones that I find which crash, and not know
if there are some others that I just haven't come across in testing yet.
Obviously Scott knows which callbacks he implemented. Is there a published
list anywhere?
TIA,
Ben Rubinstein | Email: benr_mc at cogapp.com
Cognitive Applications Ltd | Phone: +44 (0)1273-821600
http://www.cogapp.com | Fax : +44 (0)1273-728866
More information about the metacard
mailing list