Subj : Re: Change TinyId to int16
To   : netscape.public.mozilla.jseng
From : Thorsten R
Date : Sun Feb 27 2005 04:05 pm

> You should question your "need".  There are many ways to map id to
> index, including doing it yourself with a hash table.

We have internal arrays with "fields", which are data values. They are
published to SM as properties of a class. Using extra hash tables is more
than just suboptimal. And I'm really asking myself, why this ID is only
8-bit in the external API and 16-bit in the internal API of SM.

> We're not going to make an incompatible and unnecessary change at this
> point.  If you want to play nicer, you should bring up the requirement
> (the "need" I question above) before hacking.  Otherwise you may marry
> your changes and we may never converge.

If you leave the property struct as it is, there is no incompatible change -
at least on Win32 all int-based parameters are passed as 4-byte on the
stack - so existing applications run with the modified DLL like before
(without recompiling). For other platforms: I don't know.

We will keep the change, because it is necessary. (the name of our compiled
DLL will not confict with the official JS DLL).

Thorsten

.