Paul Fisher wrote:
> Yet another option is to stick the entire Unicode attribute database
> into memory -- it's around 21k.
I think the majority of users would be willing to pay for the 21k (which is
probably far less than the JDK code requires thanks to your smart packing
scheme). Is there an elegant way to make this configurable at compile or
runtime? I'm not an expert on how classloading works, but could the Unicode
data be compartmentalized so that the 21k is loaded iff any Unicode
attributes are accessed?
Wes
