No, wait ... I have no idea at all what you're referring to. I just realised that i had a typo when i ran what you posted. AFAICT, doing this:
$foo = $foo; $bar = $bar; $something_else = $something_else; ... has absolutely no effect. I thought you were trying to point out some PHP strangeness even though the lines are completely unnecessary. If, instead you mean the, "Undefined variable: something_else ..." notice, that's Cake doing that. And that's precisely what this is all about. Cake's set() method passes the var name to Inflector, which camelizes it. Again, though, the workaround is to pass false as the second param. On Tue, Jan 27, 2009 at 3:58 PM, brian <[email protected]> wrote: > Yeah, I guess that screws with the symbol table. I agree that seems a > bit buggy. But I don't follow your logic here. I'm not doing what you > have in your example. It's Cake, not PHP, that has the unexpected > behavior in my case. > > Anyway, I figured out how to get around it, documentation be damned. > > On Tue, Jan 27, 2009 at 2:15 PM, rtconner <[email protected]> wrote: >> >> I think the issue is PHP and not Cake. >> >> To demonstrate the problem, try this... >> >> public function setStuff($foo, $bar, $something_else) { >> $foo = $foo; >> $bar = $bar; >> $something_else = $something_else; >> $this->controller->set(compact('foo', 'bar', 'something_else')); >> } >> >> And I have no idea why PHP behaves that way, but it does. >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
