Don't want to start a whole discussion again on this, but the adoption of OO paradigm eliminates the need for most globals in the first place.<br><br>That's the advantage, along with a lot of others...<br><br>Victor Kane<br>
<a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a><br><br><div class="gmail_quote">On Sat, Jun 14, 2008 at 12:09 PM, Adrian Rossouw <<a href="mailto:adrian@bryght.com">adrian@bryght.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
On 14 Jun 2008, at 5:00 PM, Syscrusher wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
If we're talking about that kind of a major change, is it time to<br>
revisit the question of whether Drupal should use PHP's OOP features,<br>
now that the PHP language has better OO support than it did several<br>
years ago?<br>
</blockquote></div>
how is that a major change ?<br>
<br>
we simply find all occurences of global and $GLOBALS, and replace it with context_get.<br>
<br>
we will also be able to track whenever global variables change because you need to use context_set to use them,<br>
so it's impossible to fsck up your site by accidentally wiping out globals.<br>
<br>
</blockquote></div><br>