Efficiency
Since RWClassID is more efficient in both time and space than RWStringID, you may wish to continue using it wherever possible. RWStringIDs are useful:
*For organizations that need to generate unique identifiers for many programming groups;
*For third party libraries that need to avoid clashes with other libraries or users;
*Anywhere the self-documenting feature of RWStringID adds enough value to compensate for its slight inefficiencies.
RWStringIDs are generated for all RWCollectable classes that are compiled under the current version of the Essential Tools Module. This additional code generation has only minor impact on programs that do not use the RWStringIDs. The RWFactory will be larger, to hold lookups from RWClassID and RWStringID; and startup time will be very slightly longer, to accommodate the addition of the extra data to the RWFactory.