Hi Greg,
>
>
> What I am saying is that in a hybrid Object Oriented environment, whether it is Delphi, C++, or VFP, methods are methods and properties
are properties. If you
Yes, but should you not realise that information intensive applications
from a special challenge to OO in general, because of the lack of
support for persistent objects.
> What you need to realize is how a (for instance) customer class is modeled to the business app being written first whether through user
cases or whatever, then
.... and so where my doubts arise is in our ability _today_ to map any
obect model into Foxpro, C++, Delphi etc., and consequently by departing
from more traditional analysis approaches (DFD,ER etc) to end up with
system requirements are that not or ill suited for the programming
environments that are available for us, again _today_.
>
> I'm not here to argue, just to learn ,as I don't have the answers, I am still learning. It's nice to read opinions, we will form our own
judgements to arrive
>
Please read my postings in exactly the same spirit. I think your
investigation is courageous, and although I am not personally convinced
that OO _is_ necessarilly the way to go in the future, I certainly feel
the pressure to prepare myself for the day ... I've been badly wrong
before!
Marc
If things have the tendency to go your way, do not worry. It won't last. Jules Renard.