Reply-To: "Kevin Aylward"
From: "Kevin Aylward"
References: <email@example.com> <01c2b41a$cafe2d80$a893eb41@stupidwin95>
Subject: Re: To C or not to C
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-Inktomi-Trace: public1-pete2-5-cust22.pete.broadband.ntl.com 1041784915 30680 126.96.36.199 (5 Jan 2003 16:41:55 GMT)
Date: Sun, 5 Jan 2003 16:41:49 -0000
NNTP-Posting-Date: Sun, 05 Jan 2003 16:41:56 GMT
D Poinsett wrote:
> Hi Kevin,
> "Kevin Aylward" wrote in message
>> The idea of not using floating point for certain types of
>> mathematical software, e.g. spice, mathcad etc is plain daft.
>> Indeed, you want higher levels mathematical constructions, e.g. a
>> class for complex numbers to further reduce the details of routine
>> multiplication and division. There is simple far to much going in in
>> these types of programs to bother pissing about with something as
>> basic as what a number is.
> With the luxury of large memory and computational resources, you are
> spot on right. In fact, some projects demand those kind of resources.
> For smaller projects, especially embedded designs, those resources
> would be inappropriate. In many cases, I could not afford the power
> consumption budget let alone physical size and cost of anything but a
> small 8-bit device. When speed and code-size resources are limited,
> the choice of math routines can become an important consideration.
I agree, its horses for courses, but I would probably try and change the
course so that C/C++ could be used. One reason is that for every person
who can do asm, there are probably 10-100 times as many who can do C.
I would agree that the distinction is not really between embedded verses
say, Windows or Unix applications, as there are large numbers of
embedded applications where 100k to 1Meg+ code sizes are the norm. Its
the size of the project that matters. I would say that most projects
nowadays are the big, difficult ones, all the easy ones have been done,
well part from yet again another washing machine comtroller, but who
wants to do them:-)
For me personally, I simply would not want to be involved in a project
where you could only use 1k of RAM. Maybe some might get a kick from
fitting it all in, but realistically, I don't see that there's any real
meaty technical challenge to get ones teeth into with such constraints.
I find it much nicer to be working on systems where you don't have to
worry about the lower level mundane details. There is a lot more
interesting stuff going on, imo.
SuperSpice, a very affordable Mixed-Mode
Windows Simulator with Schematic Capture,
Waveform Display, FFT's and Filter Design.