linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mat Harris <mat.harris@genestate.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: migration from perl
Date: Thu, 15 Aug 2002 17:10:05 +0100	[thread overview]
Message-ID: <20020815171005.B32743@genestate.com> (raw)
In-Reply-To: <20020815152939.GA1977@prester.freenet.de>; from axel@hh59.org on Thu, Aug 15, 2002 at 05:29:39 +0200

[-- Attachment #1: Type: text/plain, Size: 757 bytes --]

so am i right in thinking gcc is the same as C++?

On Thu, Aug 15, 2002 at 05:29:39 +0200, Axel Siebenwirth wrote:
> Hi Mat!
> 
> On Thu, 15 Aug 2002, Mat Harris wrote:
> 
> Look at http://gcc.gnu.org and learn C++, I'd say. Because if you know C++
> you also know plain C. And object-oriented programming is always a good 
> thing nowadays.
> 
> Regards
> Axel
> 
> > hi, i am a 'fairly' competant perl programmer but I believe that as most
> > of my work is with redhat, i should know that language it is built with.
> > 
> > can anyone point me in the right directions? what is the C equivalent to
> > perl.org? Should I learn C or C++?

-- 
Mat Harris			OpenGPG Public Key ID: CC14DD34
mat.harris@genestate.com	www.genestate.com	

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-08-15 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-15 14:35 migration from perl Mat Harris
2002-08-15 15:29 ` Axel Siebenwirth
2002-08-15 16:10   ` Mat Harris [this message]
2002-08-15 16:54     ` Glynn Clements
     [not found]   ` <20020815170931.A32743@genestate.com>
2002-08-15 16:27     ` Axel Siebenwirth
2002-08-15 16:57 ` Glynn Clements
2002-08-15 22:32   ` <Iliyan Malchev>
2002-08-15 22:42     ` +Rudymartin
2002-08-15 23:33     ` Glynn Clements
2002-08-16 15:34     ` Earl R. Lapus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020815171005.B32743@genestate.com \
    --to=mat.harris@genestate.com \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).