Re: gcc/vi better than VS
From: Star Fleet Admiral Q (Star_Fleet_Admiral_Q(NOSPAM)_at_(SPAMNOT)hotmail.com)
Date: 02/23/04
- Previous message: Jason Callas: "IntelliSense in new file"
- In reply to: Rudy Ray Moore: "gcc/vi better than VS"
- Next in thread: Rudy Ray Moore: "Re: gcc/vi better than VS"
- Reply: Rudy Ray Moore: "Re: gcc/vi better than VS"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 22 Feb 2004 21:45:45 -0500
You are comparing a Command Line product versus a GUI product - apples to
oranges. You need to compare vi/gcc to notepad/cl.exe or KDE GUI developer
tools to VS - I use both supporting both Windows, Linux and AIX machines,
and the GUI interfaces all have the same restrictions by design, not a bug.
I guess you've never been bit by compiling a large application for 30-60
minutes just to have it die because you saved the code you were editing and
the thought process (code) was incomplete.
"Rudy Ray Moore" <rudymoore@hotmail.com> wrote in message
news:enihxzm8DHA.2480@TK2MSFTNGP10.phx.gbl...
> Here is one thing I like better about using gcc/vi over visual studio:
>
> When compiling or linking with gcc, the text editor (vi) never locks up.
>
> However, when compiling/linking with visual studio, sometimes the text
> editor locks up and I have to wait for cl.exe or link.exe to finish
whatever
> it's going to get control of my editor again. :(
>
> gcc/vi proves that it is possible to edit text while compiling, so I have
to
> ask the question: Why does visual studio not let me edit text while
> compiling?
>
> I've seen this behavior on VS6 and VS7.1
>
>
- Previous message: Jason Callas: "IntelliSense in new file"
- In reply to: Rudy Ray Moore: "gcc/vi better than VS"
- Next in thread: Rudy Ray Moore: "Re: gcc/vi better than VS"
- Reply: Rudy Ray Moore: "Re: gcc/vi better than VS"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
