Date: Wed, 08 Apr 2009 08:10:20 -0400 From: William Gordon Rutherdale <will.rutherdale@utoronto.ca> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: C programming question Message-ID: <49DC942C.7090301@utoronto.ca> In-Reply-To: <139b44430904080436j7fa08015u1d77c38c51e2583a@mail.gmail.com> References: <139b44430904070241j5227d178jd75f6a93057a150a@mail.gmail.com> <20090408085042.GA54417@melon.esperance-linux.co.uk> <20090408124952.X34961@gwdu60.gwdg.de> <139b44430904080436j7fa08015u1d77c38c51e2583a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Valentin Bud wrote: > Thanks everybody for the heads up. I don't know (yet) which path i am going > to take. I know a little bit of perl so i guess i'll start reading on how > can i accomplish my goal with perl. > > thanks, > v > I've been programming for a very long time, and I can tell you that both Perl and C/C++ have done me very well. The centre of gravity keeps shifting in software, but most of the scripting languages, and the libraries they depend on, are written in C. Installing most packages from scratch usually depends on having a C compiler around and knowing how to use it. The fundamental system interfaces in all forms of Unix are written in and for C. There are always jobs out there requiring knowledge of C, especially in embedded programming. I would suggest that you can't go wrong taking the C path, and you would probably do well trying it in Perl too. -Will
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49DC942C.7090301>