Xref: news2.mv.net comp.os.msdos.djgpp:7860
From: pengzh AT ix DOT netcom DOT com (PENG ZHOU)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE and DJGPP
Date: 22 Aug 1996 03:04:29 GMT
Organization: Netcom
Lines: 41
Message-ID: <4vgint$nv1@dfw-ixnews10.ix.netcom.com>
References: <320FC47B DOT 4AB1 AT mindspring DOT com> <3216381F DOT 5B8D AT intellinet DOT com>
NNTP-Posting-Host: pas-ca12-16.ix.netcom.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In <3216381F DOT 5B8D AT intellinet DOT com> "James S. Blachly"
<stew AT intellinet DOT com> writes: 
>
>Joshua Cannon Butcher wrote:
>> 
>> 7)      And for everyone in General, why do you have to stray away
from
>> industry standards?  Calling object files .O files instead of .OBJ,
>> calling C++ files .CC instead of .CPP, and .a instead of .LIB for
>> library.  HELLO!  Its not copyright infringement to use the same
>> extensions, and it would make the transition for existing C and C++
>> users to use.  This is quite frankly scaring me, and almost makes me
>> want to pay the $500 for Borland C++ 5.0 so I can have the
"standard" of
>> the computer programming industry.
>> 
>> I just do not understand, and would like to.  Thank you for your
time...
>> 
>> Joshua
>Well, as far as "industry standards", the extensions .o .a and .cc
were
>around in UNIX _BEFORE_ the dos convention of .obj and .lib (and
cpp).
>Please try not to sound so angry and all knowing without first under-
>standing the situation.
>
>As far as three file extensions making you want to pay $500 for
another
>compiler, well, that's your business.
>
>-james.
>James S. Blachly
I would I agree, the UNIX .o .a .cc comes before dos, the guys at
Borland/Microsoft simply changed it for DOS to make you think it's the
standard of C.  But you must know, programming is not like C or any
other language.  It is not affected whether the extensions are .cc .o
a to .cpp .obj .lib or not.  Programming is simply a way to make the
machine(or ask) to do what you want.  Not a bunch or standards on file
formats.  It doesn't matter!  As lone as it can handle ANSI C programs,
it is a Standard Compiler.