I was wondering about that, but is it really wrong?
From what I found in the "BSD General Commands Manual":
Any arguments specified on the command line are given to utility upon each invocation, followed by some number of the arguments read from the standard input of xargs. The utility is repeatedly executed until standard input is exhausted.
and
-P maxprocs
Parallel mode: run at most maxprocs invocations of utility at once.
The way I interpret that is that you could run xargs in parallel mode, but by default the "utility is repeatedly executed" in the same process.
turns out my .bash_history is clipped at it's default size-limit (500 lines). So I'll change that to gather more data for next year. My results started with:
147 clang++
77 ls
54 cd
15 gs
14 rake
13 vim
...
where gs is short for "git status"
...and thanks for the hint about the substitution! I updated it on my page.
Most of what I learned about C++ I got from books, blogs and some great C++ guys (mostly from the boost community). I have to admit I did not read the standard at all.
could you give an example of a case where you hit undefined behavior since I hardly seem to recall a case where that bit me in the past? (I'm mostly working on embedded systems (PPC & ARM))
The cases that come to my mind for C++ all involve initialization...
@fferen, @jlarocco, @Mon_Ouie, @deckiedan: I know you can probably set up all you need within the blink of a second (using emacs or vim or a template setup).
Actually I'm so hooked on this idea I even wrote my own rake based C/C++ Buildsystem (https://github.com/marcmo/cxxproject).
But still sometimes I prefer not having to set up anything and not having to clean up anything after I end my experiments. ... Idea - drop into REPL and try out - exit - done.
I'd say error recovery could be better. You often get kicked out of the session and than your environment is lost.
Also: they claim the 'auto' keyword is implicit, does not seem to work for me.
But it's pretty cool to use!