[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: To OO or not to OO?
- To: Ken Tilton <firstname.lastname@example.org>
- Subject: Re: To OO or not to OO?
- From: email@example.com (Steve Strassmann)
- Date: Sun, 5 Mar 1995 20:36:35 -0500
- Cc: firstname.lastname@example.org
- Sender: email@example.com
At 7:16 PM 3/5/95, Ken Tilton wrote:
>I am porting (OK, rewriting <g>) my sort-of expert-system app from straight C
>I was all stoked to see what my app would look like in OO form, but now I am
>getting cold feet. My worry is performance, especially in regard to generic
Most people go through an exploratory phase first, and save the
performance-tuning for last. Especially when you're writing a new sort of
program, premature optimization will make your program needlessly baroque
Your best bet is to go ahead and write in straight CLOS in a natural and
clear style, just to get all the functionality working first. You'll think
of many cool features along the way to add, I'm sure. Then, approach the
system as a whole and try to identify the critical parts where performance
Unlike C, you'll find you can re-architect substantial subcomponents of your
program without destroying the rest. You may be astonished to discover that
you spared yourself much agony in your design because the bottlenecks are
not where you would have thought.