According to the actual grammar and implementation, the right way to do this is using:

Foo::lol as protected dontKnow;


Stefan Marr, is supposed to work the code as the bug reporter tried it?

Interesting question.

I suppose it could be legal (but obviously it is currently not implemented).
It looks kind of ugly to me, since it is less concise.
But well, all the traits use definitions should be declarative and orderless, so 
if it is possible to do something with two separate declarations then people 
might expect that it works.

Not sure whether we want that... 
But anyway, a good catch, thanks.
Stefan

class Boo {
  use Foo {
    Foo::lol as dontKnow; 
    dontKnow as protected;
  }
}

To me this would do the following:
Use "Foo", set "Foo:lol" as "dontKnow", and then set "dontKnow" as "protected"

Meaning that I should be able to call $boo->lol, $boo->dontKnow, or $boo->protected to accomplish the same thing.

Otherwise it should throw a method does not exist error if the "as" is supposed to rename the function.

Hm, today I feel like it is not a good idea to allow

use Foo {
  Foo::lol as dontKnow; 
  dontKnow as protected;
}

Because we will end up with chains like this:

use Foo {
  Foo::lol as dontKnow; 
  dontKnow as foo;
  foo as bar;
  bar as baz;
}

And I do not see the use case for it, while I see readability problems.

This is all equivalent to:

use Foo {
  Foo::lol as dontKnow; 
  Foo::lol as foo;
  Foo::lol as bar;
  Foo::lol as baz;
}

Which IMHO is a lot clearer. Every level of indirection is another level of added complexity, and I do not see a relevant use case at the moment.

So, I will regard this as something that should not work.
Not sure yet how to design it properly. Will look at it.

This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.

 For Windows:

http://windows.php.net/snapshots/
 
Thank you for the report, and for helping us make PHP better.

Fixed in SVN rev 319483.

These kind of two-step declarations are now disallowed and cause a compilation 
error.

The reason is that it invites inconsistencies like:

Foo::lol as dontKnow public; 
dontKnow as protected;

Possible inconsistencies, as well as the 'dont repeat yourself' principle are 
the reasons to disallow it completely.