public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Thomas D. Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: free programming language
Date: Tue, 12 Mar 2002 11:10:29 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0203121107560.2670-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0203110937270.13689-100000@babel.hpcc.noaa.gov>

Hi, I certainly agree here. Basic is not a good choice. Perl might be a 
better language to try. At least it offers some good programming habbits, 
and is a modern language to boot.
I started out by learning C, and it really gave me a real pointer on how 
to program. There are vary books out there that teach c and make it as 
easy as possible to learn.
 

 On Mon, 11 Mar 2002 
jwantz@hpcc2.hpcc.noaa.gov wrote:

> Hi Greg,
> I definitely disagree.  BASIC teaches bad programming habits like 
> FORTRAN i.e. non-structured programming.  The problem with C is not the 
> language, but that most people learning C start by reading Kernighan and 
> Richie.  I have been programming in C since 1986 but it took me almost 
> half of that time to unlearn bad habits I picked up from BASIC and 
> FORTRAN.  Now, one could make a case for Pascal as your first language 
> but I really think BASIC is a bad idea.  Sure, you might be able to 
> accomplish certain tasks easier in BASIC than in C, but the time you 
> spend in learning C will make you a much better programmer in the long 
> run.
>      Jim Wantz
> On Sun, 10 Mar 2002, Gregory Nowak wrote:
> 
> > Since we're on opinions, in my opinion c or c++ are not good languages to begin with. I believe from personal experience that it is best to start with something like basic, and then move on to languages like c or c++ where the concepts you learned from BASIC will help you advance in higher languages faster.
> > Greg
> > 
> > 
> > On Sun, Mar 10, 2002 at 06:48:35PM -0500, jwantz@hpcc2.hpcc.noaa.gov wrote:
> > > Hi Alex,
> > > While BASIC sounds like a good starting language in my opinion it is 
> > > not.  First, it is very non-standard (no two BASIC interpreters or 
> > > compilers are alike).  Second, file i/o in most BASICs is really rather 
> > > painful.  As far as I know, the only BASIC widely used in WINDOWS is 
> > > Visual BASIC which is hardly free!
> > > 
> > >      Jim Wantz
> > > n Sun, 10 Mar 2002, Alex Snow wrote:
> > > 
> > > > I would use, and want to learn, basic, if there was a free Compiler and/or
> > > > IDE for basic under winblows.
> > > > ----- Original Message -----
> > > > From: "Gregory Nowak" <gnowak1@uic.edu>
> > > > To: <speakup@braille.uwo.ca>
> > > > Sent: Sunday, March 10, 2002 2:56 PM
> > > > Subject: Re: free programming language
> > > > 
> > > > 
> > > > > How about BASIC?
> > > > > Greg
> > > > >
> > > > >
> > > > > On Sun, Mar 10, 2002 at 01:25:38PM -0500, Alex Snow wrote:
> > > > > > Hi.
> > > > > > I am looking for a programming language for windows that is both free
> > > > and easy to learn for a beginning programmer.  Does such a language exist?
> > > > > >
> > > > > > ---
> > > > >
> > > > > _______________________________________________
> > > > > Speakup mailing list
> > > > > Speakup@braille.uwo.ca
> > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > >
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



  parent reply	other threads:[~ UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Alex Snow
 ` Janina Sajka
   ` jwantz
 ` Gregory Nowak
   ` Alex Snow
     ` Gregory Nowak
     ` jwantz
       ` Gregory Nowak
         ` jwantz
           ` Janina Sajka
             ` jwantz
               ` Thomas D. Ward
             ` Angelo Sonnesso
           ` Pete
             ` jwantz
               ` Janina Sajka
                 ` jwantz
                   ` Janina Sajka
                 ` Pete
                   ` Charles Hallenbeck
                     ` Pete
               ` Rich Caloggero
                 ` Alex Snow
                 ` viruses Alex Snow
                   ` viruses Pete
               ` free programming language Pete
                 ` jwantz
           ` Brian Borowski
             ` Charles Hallenbeck
             ` Gregory Nowak
           ` Steve Holmes
           ` Thomas D. Ward [this message]
         ` Yvonne Smith
     ` Ron Marriage
       ` Pete
         ` Charles Hallenbeck
           ` Pete
         ` Ron Marriage
           ` Pete
         ` jwantz
           ` Pete
             ` Alex Snow
           ` Gregory Nowak
             ` jwantz
               ` Janina Sajka
                 ` jwantz
         ` Gregory Nowak
           ` Pete
             ` Janina Sajka
               ` google randy turner
                 ` google Igor Gueths
                   ` google Janina Sajka
                     ` google Ann Parsons
                 ` google Ann Parsons
           ` free programming language jwantz
       ` Charles Hallenbeck
         ` randy turner
           ` Charles Hallenbeck
       ` jwantz
         ` Ameer Armaly
 ` Igor Gueths
 ` Ameer Armaly
 ` Angelo Sonnesso
 ` Thomas Ward
   ` jwantz
   ` Alex Snow
     ` Gregory Nowak

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=Pine.LNX.4.33.0203121107560.2670-100000@localhost.localdomain \
    --to=tward@bright.net \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).