Re: Evolution of PL/I
- From: "Donald L. Dobbs" <donaldldobbs@xxxxxxx>
- Date: Sat, 22 Apr 2006 20:15:11 -0700
adaworks@xxxxxxxxxxxxx wrote:
"LR" <lruss@xxxxxxxxxxxxx> wrote in message news:44480b8e$0$3694$cc2e38e6@xxxxxxxxxxxxxxxxx
Did you have a bad experience with OOP?
I use OOP often. It is an excellent approach to some kinds
of problems. It is not the only approach. My problem is
with those who regard OOP as the only way to do things.
For some kinds of software, OOP is exactly the right thing
to do. However, OOP carries a fair amount of overhead
in some implementations. I am sometimes required to do
problems related to hard, real-time software. The alacrity
of interrupt handling can be a controlling factor. Depending
on the requirements of the problem at hand, I may need to
choose an alternative to OOP.
For small, microcontroller problems, OOP carries too much
overhead. PL/M, Forth, C, or Assembler are often far better
choices than Ada, C++, and Java or, dare I say it here, PL/I.
I take exception to your inclusion of PL/I in the above list as NOT one of the better choices. I doubt if I still have the issue laying around but in the early '80s Byte Magazine ran an article with the results of several benchmarking tests. Digital Research's (Dr. Gary Kildall) PL/I sub-subset G implementation on 8080 and x86 PC platforms outperformed every other language available at the time for PCs. I still use it for various projects because of its lean and mean approach to clean code generation.
.
We programmers are just a bunch of worker-bees with a special
skill-set. The programming languages, software development
methods, and maintenance gadgets, are just tools in our toolbox.
We need to understand when to select the right tool for the
right job.
Richard Riehle
- Follow-Ups:
- Re: Evolution of PL/I
- From: robin
- Re: Evolution of PL/I
- From: adaworks
- Re: Evolution of PL/I
- References:
- Re: Evolution of PL/I
- From: adaworks
- Re: Evolution of PL/I
- From: henrik . sorensen
- Re: Evolution of PL/I
- From: Lady Margaret Thatcher
- Re: Evolution of PL/I
- From: robin
- Re: Evolution of PL/I
- From: adaworks
- Re: Evolution of PL/I
- From: Richard Brady
- Re: Evolution of PL/I
- From: adaworks
- Re: Evolution of PL/I
- From: LR
- Re: Evolution of PL/I
- From: adaworks
- Re: Evolution of PL/I
- Prev by Date: Re: Decoupling I/O; was Paper on PL/I
- Next by Date: Re: Decoupling I/O; was Paper on PL/I
- Previous by thread: Re: Evolution of PL/I
- Next by thread: Re: Evolution of PL/I
- Index(es):
Relevant Pages
|