2014-12-18, 07:10:47
no but i am glad you brought this up, since i added 2 arguments already to this function and that might cause issues if I want to add this.
however i am not entirely sure what this thread was attempting to solve, seems most of the discussion is on eval return values ???
components are eval'd, essentially anonymous functions
meaning there is no parameterization possible
I would simply pass func_args to the eval using a static variable for now.
Ideally components would be class methods that can have objects passed into them, since we still require php 5.2 and I dont feel like implementing janky old class constructs, I would just hack this in with an object and let you get it via $self or $this, instead of an actual reflection class or whatever the best solution would actually be in 5.3+
another solution would be to see if we can slip an extract into the code, and simply extract your argument array into the scope of the component.
extract is dangerous but shit we are already inside an eval, soooooo..
solutions welcome
however i am not entirely sure what this thread was attempting to solve, seems most of the discussion is on eval return values ???
components are eval'd, essentially anonymous functions
meaning there is no parameterization possible
I would simply pass func_args to the eval using a static variable for now.
Ideally components would be class methods that can have objects passed into them, since we still require php 5.2 and I dont feel like implementing janky old class constructs, I would just hack this in with an object and let you get it via $self or $this, instead of an actual reflection class or whatever the best solution would actually be in 5.3+
another solution would be to see if we can slip an extract into the code, and simply extract your argument array into the scope of the component.
extract is dangerous but shit we are already inside an eval, soooooo..
solutions welcome