Re: [Pki-devel] [PATCH] 0017-call-statics-statically

On 12/05/2011 10:41 PM, Ade Lee wrote: I agree it looks wrong, but the change is actually in keeping with haw the pattern vairable was used. I think the mistake is that pattern should not be static. Changing it from static to private does not bring in any compilation warnings but that constructror in general looks wrong NAME = name; OID = oid; mConfig = config; those are all statics. the problem is, I think, with the NAME field. I was digging through that during the Generics cleanup and here's what I think is supposed to happen: for most extensions, they use the name as a static field for al ook up: crete a new instance of this kind of class for that extension, the vast majority of them have NAME match the classname...some with the word extension, some without. GenericASN1Extension does not work that way. Generic is defined at run time, so this implementation says to me that there can really only ever be one extension defined, but nothing ever enfroces that so I think that this change, while weird, is strictly speaking correct. I suggest we make the change, and open a ticket to deal with the Statics in this class. Here the static is a key used, and should be a constant 0. Changing it to the proper naming convention. Updated patch attached.