Warning: avoid using 'g' as a variable name...

chrisjj

... unless you want an accidental out-of-scope assignment to be not faulted, and cause mystery NullPointerException on graphics calls.

https://github.com/processing/processing/issues/5407

Anyone have a complete list of toxic variable names to avoid?

GoToLoop

If we always declare the variables we're gonna use, they won't conflict w/ existing 1s. :-\"

jeremydouglass

As @GoToLoop says, the general solution is to declare your variables. If you want the complete list of everything that could be accidentally redifined scope, the ultimate place to check is the source code.

- https://github.com/processing/processing/blob/master/core/src/processing/core/PApplet.java#L10829

A close approximation (and much easier read) is the JavaDoc documentation. g is listed in PApplet (along with a lot of other things!). The JavaDoc also has an alphabetical index.

• http://processing.github.io/processing-javadocs/core/
• http://processing.github.io/processing-javadocs/core/processing/core/PApplet.html#g

We actually talked about g in a recent thread of yours earlier this month.

GoToLoop

And as I had already mentioned there: L-)
https://Forum.Processing.org/two/discussion/26265/how-can-i-get-a-transparent-arrow-without-the-shaft-showing-through-the-head#Item_11

BtW, a more formal way to get PApplet::g field is by calling PApplet::getGraphics() method.