No I wouldn't use properties, Arrays for params is good and we use them all the
time but having multi-mutli-dimensional arrays is where it becomes
counter-intuitive. It also appears you have sub arrays that refer to other
arrays by name. Seems needless to me.
-Original Message-
From: Ch
On Wed, May 16, 2012 at 8:15 PM, Michael Sole wrote:
> I would love to be able to write new semantics for configs or at least
> propose them and I will get working on them right away.
You are welcome!
>As for backwards compatibility you could add a new/old flag that would
>determine the config
I would love to be able to write new semantics for configs or at least propose
them and I will get working on them right away. As for backwards compatibility
you could add a new/old flag that would determine the config params type that
would default to old if not specified.
Logger::configure($l
Hello Michael,
On Wed, May 16, 2012 at 7:46 PM, Michael Sole wrote:
> Thanks!
>
> Not sure why this isn’t better documented. If multiple arrays didn’t make my
> eyes bleed I would offer to doc this better. However it seems a more
> intuitive approach would make more sense. Something like:
>
>
Thanks!
Not sure why this isn't better documented. If multiple arrays didn't make my
eyes bleed I would offer to doc this better. However it seems a more intuitive
approach would make more sense. Something like:
Array('logger' => array('param'=>'value', 'param2'=>'value'));
Or something li
