No way fc34.
Believe it or not, there are other languages much more suitable than BASIC. In fact BASIC was a good alternative (along with Fortran
) during the eighties, since it was available for "microcomputers" (personal computers of the time).
has always been a better alternative and still is.
Right now, you'd better begin with a scripting language like Python
, which interfaces nicely with C. C
isn't a bad alternative to start with if you have a teacher
. You should have a teacher anyway.
All the good programmers (not amateurs) I know have studied at least some programming at the University (E-Eng, CompSci, Maths, and even Physics). A good, qualified teacher is always a good thing.
A strong background in mathematics is necessary
for a professional Computer Scientist or Electrical Engineer (of course other scientists apply too).
You don't figure out complex algorithms without reinventing the wheel if you're not good at maths. I don't mean 'pro' level in the sense of hacking pages together in PHP or coding a flashy demo in assembler. But rather things figuring out quasi-optimal algorithms for space partitioning (like Carmack did for Quake) or applying n-dimensional packing algorithms for fast transmission over copper lines, in modern modem firmware.
If x = 1 Then
Print "Hello World!"
If (x == 1)
And y the heck would you need a ; after each line? Many times when writing a few hundred lines of code and miss 1 ;, the compiler spits junk at me, it can take hours to find the error
With any half-way decent compiler you should get your error just pointing to the next sentence after the lack occured.
BTW you don't need a semicolon after each line. You use semicolons to separate sentences in C . Some knowledge about parsers is very clarifying, but that doesn't come in "H4x0rz J0hnny's C HOW-TO". You can put several sentences in the same line in C (but it's often frowned upon to do so).
That shows pretty well what we're talking about. If you think the need of ; to separate sentences is a big language difference [or '==' as 'equal' ('=' as 'assignment')] you're a bit off-topic.
Visual Basic is not good examples of BASIC. It's quite different to most old'skool BASICs (lack of standarization is yet another problem with BASIC). Probably QB is a bit better example. Old 8bit computers' BASIC and QB are what those boffins were probably talking abut.