15 Oct
2011
15 Oct
'11
11:41 a.m.
On 15/10/11 2:12 PM, Fred Cisin wrote:
In C*, you can do that, indeed. In C*, it is possible to write code
without buffer overflows, memory leaks, or segfaulting bugs of any kind,
if one cares to invest enough effort.
The point is that it's a lot of unnecessary work for no real payoff.
Higher level languages lets one turn attention sooner to the problem
domain (and besides, typically offer more powerful modelling abstractions).?
Does this really need spelling out??
--T
* substitute "assembly language" if preferred.
? I'm not saying use HLLs for ALL applications where C* is used. Just,
say, 95% of them.
>
<pedantic>
> ...
> In C, if you want ANY error checking, then YOU have to put it in, thus
> making it an inappropriate language for beginners to write operating
> systems in.
> </pedantic>
On Sat, 15 Oct 2011, Toby Thain wrote:
Even moreso, applications - the point I was
trying to make earlier.
In C, you can have as much and as thorough error checking as you want.
<RANT>
The REAL problem is that too many people who are employed as
programmers don't understand the importance of error checking,
and it isn't adequately taught in college classes!
In MY "Data Structures and Algorithms in C" class, there were COMPLAINTS
that I spent class time teaching error checking as a fundamental component
of all algorithms.
</RANT>