Re: Command line compiler

Some people just don't believe in modern technology. I was apalled, when I returned to
the University environment in 1990, that when I left in 1980, the state-of-the-art in
software development was the "cc" command and "cdb" as a debugger (one of the more
horrible debuggers to have ever been written). When I returned in 1990, the
state-of-the-art was the "gcc" command and "gdb" as a debugger (gdb copied all the flaws
of cdb; the solution of the free software community is to continue to propagate Really Bad
Ideas into perpetuity). And, as far as I can tell, there has been no progress in the
intervening 16 years in the Unix world. (In 1990, I was already doing better than this; in
fact, I ended up doing all my development on my 33MHz PC, which compiled faster than the
$60,000 IBM workstation in my office; besides, on my PC, the compiler worked, the linker
worked, and the debugger worked, all of which were rather important to me, and none of
which worked on the IBM workstation; the debugger on my PC [codeview] was of vastly better
quality as far as the user interaction than gdb, even if gdb had worked right).

There seems to be an aura of "real programmer" in the use of these rather primitive tools.
Frankly, I much prefer living in 2006 with 2006 tools than in 2006 with 1980 tools
(actually, the tools were probably about 1978). Of course, VS.NET kind of interferes with
my attitude, but that's because it is a giant step backward in IDEs.
joe

On Thu, 1 Jun 2006 15:21:31 -0600, "Jonathan Wood" <jwood@xxxxxxxxxxxxxxxx> wrote:

I realize you are free to use whatever approach you like.

However, as someone who is comfortable with compiling in the IDE, I can't
imagine why you'd want to eliminate that in favor of a command line compiler
and makefile.

I recall the days where I created a makefile and ran nmake. All I can say is
"thank god those days are over."
Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.

Relevant Pages

  • Re: VM as target, was Is Assembler Language essential
    ... In general it costs nothing - local variable addressing is simply ... compiler to figure out the constant offsets involved when/if the frame ... the code has to maintain some kind of frame ... From that starting point the debugger has ...
    (comp.compilers)
  • [ANN] ECL 9.6.0
    ... Important changes related to the usability of the debugger and ... inspector, debugging of compiled C code, handling of floating point ... Formerly ECL would refuse to print those pathnames if ... The compiler can now generate some Lisp constants as static C ...
    (comp.lang.lisp)
  • Re: Interview Embedded Software Questions
    ... Although this is NOT 100% true if we talk about the debugger! ... int x=1; ... The compiler doesn't have to be broken at all. ... it means that if z does not equal 3 it equals to something else ...
    (comp.arch.embedded)
  • Problem with the compiler? Pointers? Unknown.
    ... Is there a major bug in the Visual C++ .NET compiler version 7.1.3088 or what? ... I have one function called FullUnloadwhich checks the pointers for NULL, ... The debugger reports m_pMap as being 0xFFFFFFFF still, ... The next function accepts szFinalPath as a parameter: ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Interview Embedded Software Questions
    ... Although this is NOT 100% true if we talk about the debugger! ... int x=1; ... The compiler doesn't have to be broken at all. ... if those automatic storage objects are used then the code MUST be ...
    (comp.arch.embedded)
Loading