I'm beginning to think that Mikey has 'chosen' C already, and is looking for validation for that decision. Certainly, any attempt to suggest any of the alternatives is met with back peddling.
C might be giving you the most progress on day 1, but it is far from the ideal choice for the whole project.
None of your "problem" needs any of the capabilities of C (the low level kind of stuff), it's all string bashing of one sort or another or managing running various external programs. This puts you into expect or perl territory.
Unless you're seriously considering that this will only take 'a few days', then some time to at least more thoroughly research alternatives (more than a few hours) could be time well spent.
You did say 'months' in an earlier post.
Try as a trivial exercise - should take no more than a day for all 4.
Take the output of "ls" and find all the "file.c" files. Do a "wc -l file.c" on each one of them, then "gcc -c file.c" on the one with the most lines.
Try it in
- C
- perl
- bash
- expect
> I should point out again that I am not a 'programmer' per se
Then you really ought to give this more consideration then
"It would be more likely for me to get a PO approved for someone to write what I need than spend months doing it."
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
What I like about C is that it is -clear- ... you do something and you know what it going on. With PERL, who knows, does anyone know what the perl interpreter was written in, or, I tried to download perl but what I got was expect and tcl and who knows what else. Seems to me perl if for those that can't or don't want to C.
I suppose if I knew perl and C perl would be easier than C. I also think assy is easier than both as I -know- what is going on !