What I Wish I Had Known About Developing C/C++ From Linux Before I Started

Post by mahmud » Wed, Apr 22, 2009, 5:30 AM UTC

kmavm wrote: post #49

mahmud wrote: post #46

Earlier quoted context omitted.

"the post-modern "developer productivity" family of languages' lack of core dumps is a bug" Lisp doesn't dump core, it will drop you in a debugger prompt where you can Frankenstein your programmer to life as you wish. Forget Lisp, Scheme and other languages with full continuations will give you the entire run trace of your program in a video tape, where you rewind and fast-forward as you wish. C is not a language who…

FWIW, I don't consider CL a member of the "developer productivity" gang of languages. In practice, it is much more like a better C than it is like python: you have C's relative poverty of libraries and richness of tools. Still, I meant what I said. "Lisp doesn't dump core, it will drop you in a debugger prompt..." What if the user isn't a developer, but, y'know, a user? On the other side of the country, who doesn't c…

  (handler-bind ((error #'(lambda (e)
        (save-lisp-and-die "lisp.core"))))
           (YOUR-PROGRAM-ENTRY-POINT))

Post by kmavm » Wed, Apr 22, 2009, 5:39 AM UTC

mahmud wrote: post #51

kmavm wrote: post #49

Earlier quoted context omitted.

FWIW, I don't consider CL a member of the "developer productivity" gang of languages. In practice, it is much more like a better C than it is like python: you have C's relative poverty of libraries and richness of tools. Still, I meant what I said. "Lisp doesn't dump core, it will drop you in a debugger prompt..." What if the user isn't a developer, but, y'know, a user? On the other side of the country, who doesn't c…

You didn't read what I wrote earlier, so here is your Lisp core dump: (handler-bind ((error #'(lambda (e) (save-lisp-and-die "lisp.core")))) (YOUR-PROGRAM-ENTRY-POINT)) Autopsy is not that hard with Lisp ;-)

Post by davidw » Wed, Apr 22, 2009, 6:14 AM UTC

ramchip wrote: post #31

bf wrote: post #26

Why are we taking C/C++ programming advice from somebody who has been doing it for just over a year? And not to troll, but anyone who honestly believes vim is a better development environment than one of the mature Linux IDEs (Eclipse, Code::Blocks, KDevelop) is an idiot.

I upvoted this by mistake. But I don't believe "not to troll" and "anyone who believes vim is a better environment is an idiot" can go together. And this is coming from an emacs user ;)

Post by thingie » Wed, Apr 22, 2009, 7:59 AM UTC

derwiki wrote: post #52

thingie wrote: post #48

Earlier quoted context omitted.

The biggest problem with screen is that it breaks ordinary virtual terminal scrollback, which is something that I can live with, but…

"Ctrl-a [" will put you enter the copy buffer mode and let you scroll up

Post by ido » Wed, Apr 22, 2009, 8:21 AM UTC

silentbicycle wrote: post #16

dkarl wrote: post #12

c++filt - an absolute necessity. Also, he should have just pointed out that all IDEs are ass for C++. Java is simple enough that an IDE can be a big help, but C++ is too complicated and too slow to compile. (The remote access thing is just a matter of the work environment being adapted to one set of tools and not another -- the real issue is that text editors beat IDEs for C++.) Otherwise, an excellent list.

The real issue is that C++ is too complicated and too slow to compile. Languages that are easier to throw together a reasonable parser for (Lisps, Smalltalk, Lua, or even C) have a much lower barrier to entry for development tools. Keeping the language syntax simple enough means that somebody scratching an itch can write something useful in an afternoon or a weekend, rather than taking a team and months.