In another article I've told you about how I would like to see one rule
removed from the PEAR Coding Standards. This rule would allow developers
a bit more flexibility, while staying true to the convention.
## Working With Trees
When working with tree data structures you often need to craft them in
different ways. PHP offers a lot of functions to change the shape of arrays,
but often they only go 1 level deep. Trees can count an almost infinite number
of levels. Hence we need recursive replacements for our beloved array
functions.
## Working with trees
When working with tree data structures you often need to craft them in
different ways. PHP offers a lot of functions to change the shape of arrays,
but often they only go 1 level deep. Trees can count an almost infinite number
of levels. Hence we need recursive replacements for our beloved array & string
functions.
Since a couple of months now, I've been involved with PEAR as a
contributor. Contributing to PEAR means adhering to the
PEAR Coding Standards. Their standards have actually been thought over, and using them
for projects (also outside of PEAR), leads to consistency, and makes it easier
for many developers to understand each other's code.
In PHP, sessions can keep track of authenticated in users. They are an
essential building block in today's websites with big communities and a lot of
user activity. Without sessions, everyone would be an anonymous visitor.