that's where I like it. vc++ works, but it's functionality is limited in the 
debugging part of things.
I do love it's intelisence though.
I wasn't aware that it had issues with c++; I have only used it on my mud 
skeleton for debugging. My bias comment was more of a joke though, most sited 
people I know would rather use m$'s debugger.


Thanks,
Tyler Littlefield
Web: tysdomain.com
email: [email protected]
My programs don't have bugs, they're called randomly added features.

  ----- Original Message ----- 
  From: Thomas Hruska 
  To: [email protected] 
  Sent: Saturday, March 21, 2009 10:59 AM
  Subject: Re: [c-prog] plz hlp about graphics


  Tyler Littlefield wrote:
  > I really think his vc++'s debugger is superior is bias. :) I started 
messing with gdb a while back and totally love it.
  > 
  > 
  > Thanks,
  > Tyler Littlefield
  > Web: tysdomain.com
  > email: [email protected]
  > My programs don't have bugs, they're called randomly added features.

  Yes there is some bias. gdb is fine if you are only writing C. gdb and 
  C++, however, have had problems in the past, particularly with 
  templates. A quick Google search shows that the template problems are 
  still not resolved:

  http://tdistler.com/2008/11/13/debugging-c-templates-brekpoints-and-gdb

  VC++'s C++ debugging capabilities is still way ahead of gdb, especially 
  in the template department.

  That said, I won't deny that gdb is still pretty good and, in terms of 
  C, they are basically on equal footing. There is also a lot of support 
  for gdb on this list.

  gdb is also probably easier to use for those who are blind or visually 
  impaired due to the command-line orientation of the application and 
  probably the fairly natural fit with JAWS. I can imagine the VC++ 
  debugger being quite difficult to use in that case and see the appeal of 
  gdb over VC++ as a result.

  -- 
  Thomas Hruska
  CubicleSoft President
  Ph: 517-803-4197

  *NEW* MyTaskFocus 1.1
  Get on task. Stay on task.

  http://www.CubicleSoft.com/MyTaskFocus/



  

[Non-text portions of this message have been removed]

Reply via email to