Scott, I'm working on getting rid of it now (I'll create a different bug issue). My quick and dirty attempt to get rid of it had a few issues, so I decided to release the main typeIdArray change first. Yes, I agree, it should be able to be gotten rid of, since it's main purpose was indeed to be nothing more than an index into the typeIdArray table.
There are some special cases where it is still used, such as to decide if something is a String/JSO (i.e. there are checks in the code literally for "typeId == 2")....So, need to factor out those special cases. Also, need to understand whether it will affect deRPC stuff. Jason On Tue, Aug 10, 2010 at 2:38 PM, <[email protected]> wrote: > Q: Can Object.typeId be gotten rid of? If not, what else is it being > used for? > > http://gwt-code-reviews.appspot.com/750801/show > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
