From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3EB8E817.4090609@ameritech.net> From: northern snowfall User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3 MIME-Version: 1.0 To: 9fans@cse.psu.edu Subject: Re: [9fans] same functions everywhere References: <20030501160047.7231.qmail@g.bio.cse.psu.edu> <000c01c3147c$c7665ae0$7b83773e@SOMA> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 7 May 2003 06:03:51 -0500 Topicbox-Message-UUID: a143f1c8-eacb-11e9-9e20-41e7f4b1d025 > > >>Because I think the main problem C has is buffer overruns, and I believe >>that the main cause of that is that people use C arrays, pointers, >>which don't encode the bounds, along with standard library routines that >>discourage doing anything else >> The beauty of C is its ability to allow the programmer a very eloquent sense of flexibility with the underlying system. "Buffer overruns" are just the manifestation of bad programming, not a weakness in the language, itself. Every language has its issues, but, that's where experience and a deep understanding of how a language works comes in handy :-) Don't blame C, blame the coder. Exceptions in a C environment is basically admitting that you don't understand enough about C to promote elegant and simple solutions to complex problems in that language. Putting the blame on C, itself, is simplistic and, frankly, arrogant. Don