I think use of extract() in themes is acceptable. The simple printing of a single variable is the easiest thing in terms of what a designer has to do. I don't think we should make that any more difficult. Additionally, the "view" of most other platforms does it that way.
I recommend removing extract() everywhere except for themes. On Feb 11, 2009, at 10:38 AM, Benjamin Hutchins wrote: > I will agree with the removal of extract() on all except themes. It > simplifies the process too much for the designers. > > Also, you realize that when using themes you can already do $theme- > >varname; .. which would be better then using Theme::get() or > turning theme into an array and renaming the theme object. > > > On Wed, Feb 11, 2009 at 10:14 AM, Chris Meller <[email protected] > > wrote: > > > On Wed, Feb 11, 2009 at 9:06 AM, Sean Coates <[email protected]> wrote: > > >> How would you remove it from theme engines ? > > > > by redefining it as > > > > function extract() { > > die ("Bad, bad monkey. No cookie for you."); > > } > > I could whip up a PHP patch for it.. (-; > > Seriously, though, it could be removed by forcing themes to do > Theme::get('varname'); or even $theme['varname']; > > That sounds remarkably like my suggested implementation of a non- > sucky SuperGlobals... go figure. :P > > > Again, I know people will whine about extra keystrokes and it being > "hard to use" so I won't push it. > > S > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
