Re: How to Remove duplicates line in the txt files

On Thu, 14 Feb 2008 15:50:19 -0500, Happy Trails wrote:

> On Tue, 12 Feb 2008 19:24:01 -0600, Ted Davis <tdavis@[EMAIL PROTECTED]
> wrote:
> 
>>C++ string cl***** blow the best QBASIC string functions away - awk,
>>especially gawk, blows them both away.  C has many string functions,
just
>>not a native string data type.
> 
> The "C" stands for Cryptic!  C programmers live in a fantasy world.
Basic
> programmers live in the real world where being able to read a program
and
> maintain it are more im****tant making it run faster.  You only have to
> look at which way programmer costs have changed versus the way
processing
> costs have changed over the years to understand this.

I'll take well commented C source code over any self commenting language
any day.  Admittedly, uncommented or badly commented C is a a write-only
language, but that applies to other languages too.  I've had to debug
other people's BASIC code that was so bad I never really understood it -
one that comes to mind was about 30 lines and used letters instead of
names for variables ... and different ones for the same variable (that was
one of the bugs).

The one thing about C that most BASIC programmers never get is pointers,
but an understanding of pointers is necessary to understanding BASIC, and
any other language - whether they are visable or not, they are fundametal
to the way the language works.  For example, a string data type in BASIC
is really just a structure containing a length value and a pointer to the
array holding the characters - the name of the string variable is a
mnemonic for the pointer to the descriptor structure.  While some degree
of profeciency can be reached without understanding the language, true
competence does require that level of understanding.

> 
> C is completely useless without a zillion add-on library items, all of
> which are just as accessible to a modern Basic program as they are to a
> C program, so what's the big deal?
> 
> Anyone who can write spaghetti code can write bad C as well as he can
> write bad Basic.  But why some asshole always posts examples of that
> here to try to win some argument that nobody gives a **** about anyway
> is incomprehensible.
> 
> Wake up - we had this argument years ago, and nobody won!

-- 
T.E.D. (tdavis@[EMAIL PROTECTED]
)