The Cyber-Spy.Com Usenet Archive Feeds Directly
From The Open And Publicly Available Newsgroup
This Group And Thousands Of Others Are Available
On Most IS NNTP News Servers On Port 119.
Cyber-Spy.Com Is NOT Responsible For Any Topic,
Opinions Or Content Posted To This Or Any Other
Newsgroup. This Web Archive Of The Newsgroup And
Posts Are For Informational Purposes Only.
From: "Scott Campbell"
Subject: Re: To C or not to C
Date: Sun, 5 Jan 2003 15:17:44 +1100
Organization: Netspace Internet
References: <email@example.com> <firstname.lastname@example.org> <email@example.com>
NNTP-Posting-Date: Sun, 5 Jan 2003 04:14:59 +0000 (UTC)
X-Newsreader: Microsoft Outlook Express 6.00.2720.3000
> How many units are you planning to sell?
We hope for tens of thousands...
> What is the difference in cost of the 1K vs. the 2K part?
Not sure, that is not really my area.
> Of the two programs, which will be the easiest to maintain?
Most likely the C version, but the assembly is not that hard either.
> Are there routines that you developed that will be used later with another
chip from another manufacturer with a different instruction set?
Possible but not planned...
> How much development time have you spent on the assembler version vs. the
About 2 - 3 times more time has been spent on the C version just to cut the
size down. It was over the 2KB limit for a while.
> What is that time worth compared to cost savings in the two chips?
The program actually took 1 day to write, so we are not all that worried
about the time it takes... It is going to take a far longer time to write
the PC side of things.
> Your program is small so it may not make too much difference which way you
> go in this case but these are issues to think about especially when the
> program gets a little bigger.
Yes, we have discussed what will happen if the program gets bigger. At this
point it is finished, but we are trying to plan for future enhancements
also. It seems that the C version may be easier to maintain as the program
gets bigger, but will take far less time to exceed the 2KB limit and we do
not want to move to a 4KB chip at the moment. The assembly version can be
maintained at a little extra cost in time (which probably wouldn't be
significant), and it's size will also be smaller...
I have suggested we develop some things in C and look at the assembler
output to create the actual assembler code we will be using... We can then
cut down the assembler code for speed or size (whichever is needed)...
Go Back To The Cyber-Spy.Com
Usenet Web Archive Index Of
The sci.electronics.design Newsgroup