Subject:
|
Re: NQC programming guide
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Wed, 6 Dec 2006 12:13:27 GMT
|
Original-From:
|
linmix <linmix@gmail.com!StopSpam!>
|
Viewed:
|
3581 times
|
| |
|
|
Thanks for the link.
As for which programming language to learn, I'm sure C (or C related) is
a perfect choice. For one, as you say NQC is C based. Secondly, learning
C should give me a better insight in some of the things that happen in
my Linux machine. Java sounds interesting because it is used for quite a
few cross platform applications and because of lejos, but let's take
this a step at a time. Once I know my way around NQC I can always decide
to learn something else.
linmix
Jordan Bradford wrote:
> I think you need to learn to program in text-based languages in general, first.
> Since NQC stands for "Not Quite C," you should learn the basics of programming
> in C or C++.
>
> http://www.cplusplus.com/doc/tutorial/
>
> I'm sure someone will come in here and decry that approach and tell you to start
> with a newer language such as Java, but I disagree. C is a procedural language,
> and so is NQC. Java is an object-oriented language, a programming concept that
> takes procedural programming a step farther but will require an additional
> learning curve. C++ can do it both ways.
>
> But more importantly, NQC is a limited subset of C and C++, so it really makes
> sense to learn to program in those languages anyway.
>
> By the way, if you just want to learn enough to get by in NQC, you can skip
> everything from "pointers" onward in that C++ tutorial. If you find yourself
> "getting it" and things are "clicking" for you, then by all means continue your
> education in those advanced concepts.
>
> Caveat: I learned BASIC in elementary school, promptly forgot most of what I
> learned, and then tried teaching myself C++ in junior high. That was a failure.
> Later as a college freshman I re-learned programming in a formal computer
> science setting, and that was much more helpful to me. What I'm saying is that
> when I was starting out, having someone teaching me to program produced better
> results than when I tried learning the basics on my own. Now I'm at a point
> where self-education is equally useful, but each person is different, so good
> luck!
>
>
|
|
Message has 1 Reply:
 | | Re: NQC programming guide
|
| (...) Yep - that's definitely the case. Once you have learned one C-like language (and I'd describe JAVA, NQC, C++, Python, Pascal, JavaScript, PHP as 'sufficiently C-like') - it's quite easy to learn another. I needed to learn PHP for a project I (...) (18 years ago, 7-Nov-06, to lugnet.robotics)
|
Message is in Reply To:
| | Re: NQC programming guide
|
| I think you need to learn to program in text-based languages in general, first. Since NQC stands for "Not Quite C," you should learn the basics of programming in C or C++. (URL) sure someone will come in here and decry that approach and tell you to (...) (18 years ago, 5-Dec-06, to lugnet.robotics)
|
14 Messages in This Thread:
 
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
