-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Transfer-Encoding: quoted-printable
At 2:53 PM +1100 on 2/20/99, Andr=E9 Spierings wrote:
><<That's a great idea, but I'm concerned about the overhead
>involved with calling an external all the time,>>
>
>The calling of an external would be next in the message passing path
>after the scripts have been checked.
>There shouldn't be much overhead. I wouldn't imagine.
Using externals for commands would:
Cause us to have to prepare a CFM fragment every, single command
(or, cause a mixed mode switch!)
Make a dynamic compiler impossible
Cause the app to be more bloated than your average piece of MicroSoft
junk -- each command would have XCMD library code in it. There would
be more XCMD interface code than actual code. Ex:
Add 2 to x.
1 PowerPC instruction:
addi x,x,2
1 68K instruction
ADDQ #$2, x
Countless instructions to call an XCMD, including:
1) Conversion of x and 2 from binary to text
2) Copying that and creating a XCMD parameter
block
3) Undoing #1
4) Adding 2 to x
5) Converting the new x to text
6) Converting the new x to binary
7) Disposing of all memory allocated.
Probably gives about 80 adds/sec. My PowerPC should
pull off no less than 100 million/sec.
Please don't even think about using XThings for HyperTalk commands.
(BTW: If you don't believe me, write an XFCN in compileit to add x to y and
return the result. Then test it vs. the HyperTalk command.)
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQA/AwUBNs5mtBpQTsYMFpEsEQLHdgCgnG2bYywLLrQnKt2mVRdEv+sawlQAoOhH
CBg2SDRMlgvqR8vXfo9ix7Tf
=gCL6
-----END PGP SIGNATURE-----
