Description:
------------
Try it -- put a static variable in a trait declaration, then access that variable 
in code defined in the trait and/or defined in the "exhibiting" class.  It works 
just fine.

I spoke with Rasmus; we both believe this is fine behavior and that the 
documentation (quoted below) should be changed to make it clear that one can, in 
fact, declare a static variable within the trait definition.

Quote from: http://php.net/manual/en/language.oop5.traits.php

"Static variables can be referred to in trait methods, but cannot be defined by 
the trait."

Test script:
---------------
<?php
// So, the following works and, for my purposes, is really, really useful.

trait TTrait {
    protected static $instance = 'hello there';

    public function publicFn() {
        echo self::$instance . "\n";
	echo "publicFn\n";
    }
}

class Foo {
    use TTrait;

    public function tryMe() {
        echo "From Foo: "; $this->publicFn();
        echo "In tryMe -- instance is: " . self::$instance . "\n";
    }
}

$f = new Foo();

$f->tryMe();


Expected result:
----------------
As noted, please adjust the doc to reflect that static variable declarations are 
actually allowed.  Currently, name collisions are handled as is done for non-
static properties (i.e. E_STRICT error, as per the doc for properties).

In the future, it might be nice if the renaming clause would work for static 
variables too.