But why have WP_DEBUG there then? You can have WP_ALLOW_MULTISITE there to show a variable there and it can also provide a codex link that would allow you to see what you can do with it. Some people might not even notice the muti-site ability unless it is pointed out to them.

Some people might not even notice the muti-site ability unless it is pointed out to them.

For 3.0, that's kind of the idea. As I've said a few times before, MU is not for the faint of heart, and neither is multisite in 3.0. It'll get better in a future release, but for now we're hiding it behind a barrier because the learning curve is far too high for the average user.

We added WP_DEBUG to raise its profile. We don't need to be doing the same for WP_ALLOW_MULTISITE.