|
Posted by Thomas Mlynarczyk on 10/26/34 11:32
Also sprach Weird-beard:
> So the "perfect" OO-Script would consist on the global level of only
> class
> definitions, maybe some constant definitions or global configuration
> variables and one simple instantiation statement at the end which
> would (via
> the constructor function) start the actual processing?
>
> - The appropriate word is could consist on. Depending on your
> requirements. You dont always need such stuff.
Thus, I do not "have to" use OOP features in situations where they have no
benefits.
> - OO php is getting better. But, I dont think it is currently geared
> towards people developing only php, as you will not be able to find
> many references on oo php. Oo is not a new concept, nor it is just an
> issue of php. Php started to use it, for users who had already been
> developing oo programs, as the software developers needed it. If you
> would like to learn more about oop, you can look at any language.
> dotnet, c++, java (especially java). The concepts are the same,
> sometimes the names differ. (Although I would not recommend getting
> into Microsoft references, as most of them are a waste of time, as
> they are geared towards only dotnet architecture and usage). Good
> coding practice is not the word, the word is good object oriented
> design or architecture. Good coding practice is naming functions
> passing parameters etc. OOdesign is more.
Thanks for the suggestions!
Greetings,
Thomas
Navigation:
[Reply to this message]
|