Hello. Recently a friend of mine, who is learning programming in university for a master degree asked me to help writing a script for unix that matches a C file and opens it for reading or writing. Here is my suggested script:

#!/usr/bin/perl use warnings; use utf8; use strict; my $arguments = shift; if ( system("gcc $arguments") == 0) { #can we complie the file? print "C file.. opening... \n"; open (FH, '<', $arguments) or die("No file: $!\n"); while ( <FH> ) { print $_; #read it, edit it or whatever needed } } else { print "Not a C file\n"; }

I know that you`d suggest doing a search in file such as regex search or .c match, it`s true but actually you can`t be that verbose if it`s C file by just matching #include<stdio.h> or int main(void)... So I suggested to try compling it -- if it succeeds it`s a C file if it fails it`s other one. Opinions?


In reply to S simple C checking script by heatblazer

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.