OpCodes violate the WebKit style guidelines... and should be autogenerated Kinda two bugs in one... i guess. Am I missing something here? Why would they use foo_bar instead of FooBar? And why not autogenerate Opcodes.h using a hacked version of one of the autogen scripts from WebCore or a spankin new ruby/python/whatever-that's-not-perl verison?
We say foo_bar instead of FooBar because we want the enum values to match the way the opcodes will look in bytecode assembly dumps. In assembly-style languages, StudlyCaps would look funny. A patch that adds a brief comment explaining this would be ok if you think it is necessary. I also think autogenerating the opcode list is a good idea. We'd take a patch to do that.
This hasn't changed in nearly 3 years, so I think it is only pragmatic to consider this 'won't fix'. :-) I think we may want to revisit this position, but with no plan on making this change in the near future I don't think this bug is usefully tracking intended work for now. As such, I think closing for now is wisest.