> our tells you something is "global" where you declare the variable, but it doesn't tell you that where you use it.

I have problems to follow. our $var creates a lexically scoped alias to a package variable $PKG::var whith PKG for the current __PACKAGE__ . If you are afraid to loose count "where you use it" just limit the scope, much the same way you do with private vars declared with my.

> of a g prefix is an immediate and obvious reminder at the point of use that this is a global variable.

Then maybe consider full qualification instead of a g_ prefix.

Using $PKG::var is IMHO much clearer, and $::var is a handy shortcut for $main::var

C++ish I'd accept (but see the list of languages I've worked with on my home node).

Perhaps I was being too specific when I said "our tells you something is "global" where you declare the variable". I was more intending to suggest that using an identifier over a wide scope puts more onus on the identifier to convey meaning and that any amount of "documentation" at the point of declaration doesn't help at the point of use. A simple g prefix is a heads up that this variable has large scope: beware, here be dragons. Most of the time the extra markup to convey that the variable hails from some package or another is unnecessarly heavy handed and doesn't add much value anyway.

Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond