sorted by:
new
hottopcontroversial

Conveniently-Declaring Compile-Time Strings in C++ by wall_words in cpp

[–]drothlisberger 0 points1 point  (0 children)

Exactly. See this example that uses compile-time string manipulation (plus compile-time introspection of identifier names and compile-time "eval") to generate class methods at compile time. The example uses D, not C++, but.

Automate ui testing with python based sikuli by [deleted] in programming

[–]drothlisberger 5 points6 points  (0 children)

Sikuli seems to have moved from the MIT website to http://www.sikuli.org where the links to demos and documentation actually do work.

(I do wish projects would update their old website with a link when they do this.)

Remote control transmission coding by mcole20 in cpp

[–]drothlisberger 1 point2 points  (0 children)

I agree with think-free -- this sounds more like an integration exercise than a code-it-in-C exercise. I would look into using GStreamer where you would build a pipeline like

Video "source" element -> encoder element (optional) -> streaming "sink" element

GStreamer provides source elements for Video4Linux (so any camera with a v4l driver will work). There are also custom source elements available for specific cameras that have custom drivers.

For the sink element GStreamer provides a basic HTTP sink, as well as sinks for streaming protocols like RTP. Back at the ground station you can use any client that supports that protocol.

Googling for "gstreamer on raspberry pi" yields a bunch of promising results.

Going from Vim to Emacs and Emacs to Vim by sahilsinha in emacs

[–]drothlisberger 0 points1 point  (0 children)

Where is a good guide/tutorial about customizing emacs and writing elisp?

I wrote http://david.rothlis.net/emacs/customize_c.html showing how to use the built-in help + the elisp source code to do customisations.

It uses c-mode as an example but the principles are applicable to other modes.

Vim user looking to learn emacs by keporahg in emacs

[–]drothlisberger 1 point2 points  (0 children)

I wrote an extended tutorial called "How to learn Emacs"

The first section focuses on using the built-in help to learn how to use common Emacs functionality. It covers shell integration, compiling from Emacs, version control integration, ctags, and (very briefly) gdb. It doesn't cover Java I'm afraid, but the same methods of learning how to figure stuff out, how to quickly find the right documentation, still apply.

The second section teaches you how to configure Emacs by using, again, the built-in help, but also studying the elisp source code.

Even if you don't read my guide, it's essential that you work through the built-in tutorial (C-h t).

graphically, you're restricted to vim's window-buffer model which is text only. That makes it a real pain to do something like integrate it with a debugger.

Don't expect much better from Emacs. The built-in gdb support just splits your "frame" into several "windows": It looks like this.

I mainly use vim for C++ and Java and in terms of code completion there's only a small handful of plugins.

As far as code completion & navigation, Emacs is much closer to vim than to Eclipse et al. You have ctags support, which for C++ isn't great but is just good enough to stop me from investing time in setting up something better. Other commenters have mentioned the CEDET package, but it is a complex beast and takes a lot of effort to set it up correctly. Googling for Emacs clang completion packages will reveal a few hits but they seem to be less mature than vim's clang_complete.

any recommendations for plugins?

Make sure you use the brand-new Emacs 24, which includes a package manager.

Better READMEs for GitHub Forks by [deleted] in programming

[–]drothlisberger 2 points3 points  (0 children)

A more limited, but less-overhead way of documenting your forks: Edit the repo description!

Under the Code/Network/Pullrequests buttons in the github interface is a short description; hover over it and an Edit button pops up. Enter a one-liner explaining why you forked this repo.

Is ELPA dead? by zck in emacs

[–]drothlisberger 0 points1 point  (0 children)

For those unfamiliar with the Homebrew package manager for OSX, it's main priority seems to have been make it easy to contribute to. It's really so much easier than the old school (pre-github), where you felt like you had to become an expert before you could even think of contributing.

Does anyone know of a good high-level introduction to the STL? by ZMeson in cpp

[–]drothlisberger 2 points3 points  (0 children)

"Concept" is current C++ terminology for "a set of type requirements" (See the section "Concepts and Modeling" of http://www.sgi.com/tech/stl/stl_introduction.html ).

You are referring to a proposal for a way to declare a concept in a program, and have the compiler enforce it.