Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!david
From: david@ms.uky.edu (David Herron -- a slipped disk)
Newsgroups: comp.sys.amiga.tech
Subject: Re: C vs. Assembly
Message-ID: <13687@s.ms.uky.edu>
Date: 15 Jan 90 02:39:21 GMT
References: <1125@crash.cts.com>
Reply-To: david@ms.uky.edu (David Herron -- a slipped disk)
Organization: U of Kentucky, Mathematical Sciences
Lines: 14

A really good pattern to follow when writing code -- a pattern esposed
by the designers of C and Unix -- is:  Write in high level code, first
concentrate on getting it to work, later profile-profile-and-more-profile
to find the parts which are executed a lot, optimize *THOSE* areas.

Profiling shows where optimization will do the most good.

I shouldn't think something like a "BBS" would need assembler code.
That job doesn't seem to be a highly time critical thing..
-- 
<- David Herron; an MMDF guy                              <david@ms.uky.edu>
<- ska: David le casse\*'      {rutgers,uunet}!ukma!david, david@UKMA.BITNET
<- 
<- New official address:  attmail!sparsdev!dsh@attunix.att.com