In addition to constants that you've specified in your Java code, the constant pool (which is the thing that's limited to 64K entries) also contains entries for "class metadata" like class names, class field names and descriptors, method names and descriptors, etc. (It's when this "class metadata" gets corrupted that you see problems loading the .class file. A more insidious manifestation of the problem would be when none of the "class metadata" is corrupted, but a String "constant" is corrupted (i.e.changed to some different value).)
Kendall ----- Original Message ----- From: "Duffey, Kevin" <[EMAIL PROTECTED]> To: "Ant Users List" <[EMAIL PROTECTED]> Sent: Tuesday, August 27, 2002 16:22 Subject: RE: Working around jikes bug in large projects > Let me ask you this. Is there a reason you can't move the constants out > to a config file, such as xml or properties. At runtime you could load > the config file of the constants into a hashmap, then use that map in > your code. I suppose this isn't the best way to do it. I can't imagine > 64,000 constants in use. That is a LOT of constants. > > [...] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
