eg prefix for extension config variables
How about using eg as prefix for extension configuration variables? Some extensions do it and I have adopted the style for my extensions as well. I find it quite handy with code completion to have all extension globals coming up fast.
It was in there for three years; see r70755 and comments. That's why you've seen other extensions do it.
I don't quite understand, so it's no longer best practice to use it for extensions? Why not?
It's not that it's not best practice, it's that it snuck into the coding conventions under the radar, people read it as gospel, and now we've got $eg and ef all over the place when nobody ever really recommended it to begin with.
You can call your config globals $the_most_awsome_variable_in_the_world if you really wanted to, it doesn't matter in a practical sense.
See also Manual:Coding_conventions#Variables.
