(Gunther Birznieks) writes:
>>Excuse me, but Powerbuilder is NOT OBJECT-ORIENTED .....
>>it IS OBJECT-BASED.
>Its difficult to excuse a statement which is not really true.
>Rajeev, for all intents and purposes PowerBuilder IS OBJECT ORIENTED.
>It supports encapsulation, inheritence, non-visual as well as visual
>objects. I think the only things it does not really support (to my
>knowledge) are overloaded operators/functions and multiple inheritence.
>IMHO, this is not enough to make someone stand up and say it is
>not Object-Oriented. Object-Based means that there are objects that
>come with the program but you can not extend them or make your own.
>Visual Basic is ObjectBased because VBXes are the objects with
>and methods but you can not extend them to make your own VBXes or the
>PowerBuilder is ObjectOriented because for all intents and purposes
>99% of programmers are likely to use ObjectOriented programming for,
>There are, of course, arguements about why such and such features of OO
>programming is needed over another. But the bottom line of OO
>for what real programmers want to use it for (Inheritence and reuse of
>past code), PowerBuilder has it. SQLWindows also has an OO programming
>Now, SqlWindows and PowerBuilder aren't "SmallTalk" or "C++"
>but that does not mean they is simply "OBJECT BASED" and not "OBJECT
I disagree w/ your rebuttal. Powerbuilder and SQLWindows are NOT object
oriented. They certainly have some Object Oriented features, but that
doesn't make them true oopl. It's a marketing ploy. Try dynamic
allocation of memory in real time, such as creating datafields on a form
on the fly? if you can do it. You'll eventually hit a wall. And they
are doggy. Too much overhead 4gls. Try creating a class of datafields
that are SQL enabled? You'll blow out memory with instance variables
and dog with message processing when you need to use alot of them, not
to mention generic inefficient dynamic SQL code. It's a shame the
vendors are trying so hard to export false reality. It leads to some
real stupid programming practices w/ the tools. The languages weren't
designed for the kind of programming they are selling. So, why try to
use them as such. Use them for what they are -- business application
front ends. KISS KISS
I love C++ more than my mother, but I know it's easier to train someone
in a 4gl and get results. I also have no problem with recognizing that
we are writing the last generation of legacy code with these tools
(there are no industry standards for 4gls), so why not use it for what
it's worth rather than have hangups about these theorys of marketing...
As for SQLWindows:
Data encapsulation? Hardly -- PUBLIC only
btw, C++ is not fully object oriented either...it's a hybrid.