Re: [Phpwebsite-developers] OO vs. Procedural Programing

[Brian W. B. <br...@ap...>]

Some clarification regarding the OOP vs. Procedural section of the Road Map:

I did not intend to have this be a "closed" issue, and apologize if it appeared
that way.  I would not say that PHP's handling of classes needs to be "carefully
considered" if I did not think it needed to *be considered*.

I very much respect the opinions of our developers and would like this to be
openly discussed. I do, however, want to ensure that everyone (including myself)
has a good understanding of potential pitfalls with PHP's support for OOP:

For example:

> later versions of PHP (post 4.04pl1) have the following syntax
> $myObject =& $thatObject;
>
> $newObject =& new Widget;
>
> to deal with this issue

does not really create a "true" reference because they don't point to the memory
the other variable is occupying; PHP only interprets these variables as
references and acts differently.  The copy syntax is still being used.

On the procedural side, I wanted to underscore that procedural code is a viable
option that should also be considered.  Something I *must* consider is that the
students that participate in this program often come to us as Juniors, and their
understanding of OOP is not necessarily strong.  Ultimately, I must make use of
these students and do not wish to have the project's complexity grow beyond what
they can offer.

Once again, this debate is not closed.  All I ask is that everyone consider the
the technical details, the *entire* project, and all participants involved.

Thank You and Kind Regards,

Brian W. Brown
--
Brian W. Brown
Internet Systems Architect, ESS
Student Development
Room 269, John Thomas Hall
Appalachian State University
Boone, NC 28608

vox: 828-262-7124
fax: 828-262-2585