Re: Confessions of an "OO Foreigner"
From: Thane Hubbell (thaneh_at_softwaresimple.com)
Date: 12/31/03
- Next message: Howard Brazee: "Re: OT Golf WAS Re: CoBOL moved to OO"
- Previous message: Howard Brazee: "Re: CoBOL moved to OO"
- In reply to: Peter E.C. Dashwood: "Re: Confessions of an "OO Foreigner""
- Next in thread: Howard Brazee: "Re: Confessions of an "OO Foreigner""
- Reply: Howard Brazee: "Re: Confessions of an "OO Foreigner""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 31 Dec 2003 07:21:03 -0800
"Peter E.C. Dashwood" <dashwood@enternet.co.nz> wrote in message news:<3ff210ce_5@news.athenanews.com>...
> "Thane Hubbell" <thaneh@softwaresimple.com> wrote in message
> news:bfdfc3e8.0312301535.381e7c90@posting.google.com...
> > >
> > > Only if it is early bound (and early binding stinks IMO).
> > >
> > > Pete.
> >
> > Not true - inline method invocation works with late binding provided
> > the object reference is a universal object reference (which requires
> > late binding).
>
> What do you mean by a "universal object reference"? (Defined in
> Factory...?)
>
> I don't understand this.
>
> I tried using inline method invocation in late bound programs and it didn't
> work. Hence my post. If you know better, I'd appreciate enlightenment.
>
Bill posted about Universal object references. I have no clue why
inline method invocation doesn't work for you in some cases - I am
unaware of any restrictions.
>
>
> >I also disagree with you - performance wise, late
> >binding is bad.
>
> Yes, I know that. It depends on what you mean by "bad". It is not so bad as
> to be noticeable, in the implementations I have written. I said it was my
> opinion. It is. I arrived at it after balancing the supposed "bad"
> performance against the flexibility late binding affords.
>
No disagreement there.
> >
> > Model based programming is made possible by OO. In addition "web
> > services" are made possible by OO syntax. SOAP means Simple OBJECT
> > Access Protocol. With these advances OO - being Objects AS A SERVICE
> > - will fulfill its promise.
>
> That is already possible with components. "Web Services" are dependent on
> the adoption of MS .NET and that is by no means a given...yet. SOAP is good
> but it really adds little. The same effect is attainable with DCOM+ and DTS
> (once you get them to work properly...).
>
Web services do not require the adoption of .NET. SOAP is not .NET
only. Components and services (these will become one in the same) are
made consistent via OO - this is a good thing and is the best part of
OO - IMHO.
> Your view of OO seems limited to COBOL (where I agree it has not fulfilled
> its promise yet.) In other areas and other languages it HAS fulfilled its
> promise.
I've worked on large complex systems written in a variety of
languages. I've never seen a procedural code based system collapse
under it's own weight - I have seen SEVERAL OO systems implode.
>
> Pete.
- Next message: Howard Brazee: "Re: OT Golf WAS Re: CoBOL moved to OO"
- Previous message: Howard Brazee: "Re: CoBOL moved to OO"
- In reply to: Peter E.C. Dashwood: "Re: Confessions of an "OO Foreigner""
- Next in thread: Howard Brazee: "Re: Confessions of an "OO Foreigner""
- Reply: Howard Brazee: "Re: Confessions of an "OO Foreigner""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|