Palm Python?

[Cliff Penton]

"Will Ware" <wware at world.std.com> wrote in message
news:FxDxF7.E1D at world.std.com...
> Blake Winton (bwinton at tor.dhs.org) wrote:

<snip>

> There's actually an interesting problem with "static", as it applies
> to variables rather than functions. For variables, it also limits the
> name scope to the current source file, but it has a second meaning
> which is to ensure that the variable has a permanent address (rather
> than being, say, just a local allocated on the stack). It would have
> been good to use a second keyword for this second meaning. This hasn't
> ever actually been a problem for me in writing C code, but it's an
> interesting little design blunder.

Don't think of the reuse of static as a design blunder -- more an efficient
use of keywords ;-)

Cliff