Subject: Re: Which basic compiler to buy?
Date: Mon, 16 Dec 2002 22:16:28 +0100
Organization: Delft University of Technology
References: <firstname.lastname@example.org> <email@example.com>
NNTP-Posting-Date: Mon, 16 Dec 2002 21:16:26 +0000 (UTC)
X-Newsreader: Forte Free Agent 1.92/32.572
On 12 Dec 2002 19:12:55 -0800, firstname.lastname@example.org (andy) wrote:
I think the original question was rather : what BASIC compiler is best
for small, optimized code.
He already chose BASIC as the preferred language because he is already
acquainted with it, and will thus be able to write a good program in a
short time. (Unlike the months it would take him to master C at a
reasonable level (unless he is a genious, in that case, it won't
matter whatever he chooses 8-) ))
The BASIC vs C for dummies discussion is nice, but people don't seem
to get the point : it is NOT hard science, unless you can dig up
evidence, thus they go about arguing about which they like to use
most, and see a different opinion as an insult.
Not that I'm not interested though.
>Dennis Clark wrote in message news:<email@example.com>...
>> This thread proves the old maxim:
>> "Opinions are like @ssholes. Everybody has one and they all stink!"
>> Use the language that you are most familiar with. A good compiler will
>> produce good code no matter the language. When you understand the system,
>> you can write code that will encourage the compiler to be even better.
>And if you are familiar with no language?? What then?? A wise opinion
>would be to suggest an industry standard?? Or maybe everyone should
>have suggested that the OP learn Fortran and then write his own
>> There is no such thing as portability with embedded - The devices are all
>> different, so really not even the logic is portable if you wrote the code
>> well, you took advantage of the platform you wrote it for to optimize it.
>Bullshit. If you keep device specific information seperate from the
>core application, it is portable. All you need to do is rewrite the
>device specific code. Its the same for any platform, embedded or PC.
>That device specific code is often called drivers. ASM is about the
>only language that is not truly portable, even then, you can make it
>portable between devices in the same family.
Remove some @'s to get my emailadress.