[UPHPU] inherit scope but not contribute to?

Wade Preston Shearer wadeshearer.lists at me.com
Tue Feb 2 10:16:15 MST 2010

On 2 Feb 2010, at 10:13, Scott Hill wrote:

> On Thu, Jan 28, 2010 at 9:05 AM, Wade Preston Shearer <
> wadeshearer.lists at me.com> wrote:
>> On 28 Jan 2010, at 3:02, Daniel C. wrote:
>> I'm not going to do it. I had just ran across it in a forum while  
>> searching
>> for a solution and was wondering what the ramifications would be. I  
>> ran a
>> few tests and it actually introduced more issues in my code than it
>> resolved. I am taking a difference approach.
> What was the other approach?  Would you mind sharing what you ended up
> doing?
> I'm curious because the same thing (or something similar) has  
> happened to me
> before.

The code is part of a templating engine in a framework. There are  
snippets of code that get processed inside other snippets of code. I  
was trying to restrict the scope such that each snippet would be  
processed individually and variables would be sandboxed. I simply  
dropped this requirement.

More information about the UPHPU mailing list