dev-cpp-users

[Dev-C++] General question / remark

[Janos B. <jb...@gm...>]

After having played with Dec-C++ for a few days, here is what I see:
The IDE that Dev-C++ is so good that I should probably never use Emacs for 
programming any more. It (Dev-C++) is so much better than MVC++6.

So the only problem (as far as I and probably many other people are 
concerned) is the lack of a decent debugger. I do not know how difficult it 
is to write a MVC++6 style debugger but that debugger is excellent.
Now I just thought: The Watcom sources should be be free by now; so 
wouldn't it be possible to look at that code and learn how they implemented 
their debugger (which almost paralleled the MVC++ debugger) and write your 
own debugger. Taken the genuine devotion of the Dev-C++ team (othwewise 
they could not have created such a nice product) it would be only a 
question of until they woul produce even a better debugger.

Is this suggestion completely stupid? Is any work being done on a debugger 
vor Dev-C++?

(As for the quality of the compiler, for most applications it is not that 
decisive.)

At the moment I use Dev-C++ and for the tricky parts MVC++6. Anyway, thx 
for this great product.

-- 
EG

Re: [Dev-C++] General question / remark

[David M. <dem...@uw...>]

Well, gdb is already integrated with Dev-C++.  It doesn't have the best
interface, IMHO, so there's also the Insight frontend (available on
www.bloodshed.com/dev/) Of course, it screws up the Dev-C++ 5 betas so you
can't get rid of it.

At 04:55 PM 25/04/2003 +0200, Janos Blazi wrote:
>After having played with Dec-C++ for a few days, here is what I see:
>The IDE that Dev-C++ is so good that I should probably never use Emacs for 
>programming any more. It (Dev-C++) is so much better than MVC++6.
>
>So the only problem (as far as I and probably many other people are 
>concerned) is the lack of a decent debugger. I do not know how difficult it 
>is to write a MVC++6 style debugger but that debugger is excellent.
>Now I just thought: The Watcom sources should be be free by now; so 
>wouldn't it be possible to look at that code and learn how they implemented 
>their debugger (which almost paralleled the MVC++ debugger) and write your 
>own debugger. Taken the genuine devotion of the Dev-C++ team (othwewise 
>they could not have created such a nice product) it would be only a 
>question of until they woul produce even a better debugger.
>
>Is this suggestion completely stupid? Is any work being done on a debugger 
>vor Dev-C++?
>
>(As for the quality of the compiler, for most applications it is not that 
>decisive.)
>
>At the moment I use Dev-C++ and for the tricky parts MVC++6. Anyway, thx 
>for this great product.
>
>-- 
>EG
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Dev-cpp-users mailing list
>Dev...@li...
>TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
>https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>

RES: [Dev-C++] General question / remark

[Daniel K. O. <dan...@ya...>]

 >  -----Mensagem original-----
 >  De: dev...@li...
 >  [mailto:dev...@li...]Em nome de David
 >  Matthews
 >  Enviada em: sexta-feira, 25 de abril de 2003 18:02
 >  Para: Janos Blazi; dev...@li...
 >  Assunto: Re: [Dev-C++] General question / remark
 >
 >
 >  Well, gdb is already integrated with Dev-C++.  It doesn't have the best
 >  interface, IMHO, so there's also the Insight frontend (available on
 >  www.bloodshed.com/dev/) Of course, it screws up the Dev-C++ 5
 >  betas so you
 >  can't get rid of it.



Just install Insight on another directory, and add it to your Tools menu.
Backing-up your original "gdb.exe" also helps if you want to install Insight
on Dev-C++'s directory.






Daniel K. O.