NNTP-Posting-Date: Fri, 20 Dec 2002 13:04:52 -0600
Date: Fri, 20 Dec 2002 13:07:18 -0600
From: gary drummond
X-Mailer: Mozilla 4.78 [en] (Win98; U)
Subject: Re: Which basic compiler to buy?
References: <firstname.lastname@example.org> <email@example.com>
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
Larry Bradley wrote:
> It is possible to write terrible code in any language. And it is
> possible to write perfectly useful, very readable code in any language
> - even BASIC. The quality of a particular program is less a function
> of the quality of the programming language than it is of the qulaity
> of the programmer.
> There is nothing inherently wrong with writing in assembler. A good,
> disciplined programmer can write code that is very readable by someone
> else. I spent my early programming years as a systems programmer,
> modifying IBM mainframe operating systems, which were all written in
> assembler - most of the time is was easy to read, because it was
> written by people who knew what they were doing, and who had been
> trained in how to do it right. But when it was done badly, it was a
> nightmare to figre out.
> Choice of programming languages is a religious issue.
< C/Linux warriors snipped>
You said that better than I would have! I've supported IBM and
RCA VMOS/Univac VS/9 code that was very easy to follow. I haven't
seen ANY C that is easy to follow in the C world (read - Linux).
I prefer assembler or COBOL myself. I use BASIC (Structured
8052-BASIC) when possible, or assembler for embedded, but then
I only do it for learning or to make money from my developments.
If I was getting paid for coding, I might opt for using C and
eliminating other programmers from supporting it, which would
keep me in the loop for fixes and $$ for upgrades.
Upgrades don't exist in the C world today, just new development,
because even the original programmer would rather write it from
scratch! Hardware changes due to technology changes, or using the
latest add-on have eliminated upgrades...
But back to the original posting, what the hell does the C language
wars have to do with "Which BASIC compiler to buy?"? Use the
language that works until it can't satisfy the requirements.
If BASIC works, use it.
If it gets too slow, use a compiler.
If it again gets too slow, upgrade the chip, it's faster than
learning/using another language.
If costs rise too high to use BASIC, THEN change to another language,
which would THEN involve you in the language wars! I would opt for
learning assembler before changing hardware, or having to buy
larger hardware to support the application-it would look like
I'm trying to duplicate the Windows development... (Well, they
started in ASM and switched to C, which now means 2-6 months before
fixes, due to C's complexities-and the convoluted way the "experts"
developed the APIs (Auto Program-trashing Interfaces).