Re: [dev] Shell vs C where is the border?

2014-03-11 Thread Markus Wichmann
On Mon, Mar 10, 2014 at 09:22:39PM +0100, Paul Onyschuk wrote: On Mon, 10 Mar 2014 20:39:08 +0100 Szymon Olewniczak szymon.olewnic...@rid.pl wrote: But having so many individual programs is more harder to use that just one (we need to run more commands), so reasonable would be to combine

Re: [dev] Shell vs C where is the border?

2014-03-11 Thread Dmitrij D. Czarkoff
Markus Wichmann said: The more I read of POSIX, the more I think those options are only there because they were easy to add to some specific implementations. Actually options in POSIX are mostly those already found in some specific implementations - the main idea behind POSIX is to create a

[dev] Shell vs C where is the border?

2014-03-10 Thread Szymon Olewniczak
Hi, I was recetly wondering about the use cases of C and shell. I've seen that this topic appears several times mostly when discussing sbase. Some of you probably knows ffmpeg, software that allows to convert media files between various formats. Imagine now that we have several smaller tools that

Re: [dev] Shell vs C where is the border?

2014-03-10 Thread Ryan O’Hara
On Mon, Mar 10, 2014 at 12:39 PM, Szymon Olewniczak szymon.olewnic...@rid.pl wrote: So what solution would be better in your opinion? When we should use shell scripts and when write new C programs to achieve our goals? When it makes sense.

Re: [dev] Shell vs C where is the border?

2014-03-10 Thread Paul Onyschuk
On Mon, 10 Mar 2014 20:39:08 +0100 Szymon Olewniczak szymon.olewnic...@rid.pl wrote: But having so many individual programs is more harder to use that just one (we need to run more commands), so reasonable would be to combine all this commands to one script which would do all this work