is indeed a good start. It´s got several snags and peculiarities, but nothing that can´t be mastered. It´s the default for most of today´s application and operating system development. C++ compilers are available for practically every platform or purpose.
C is a subset of C++; But the "++" part (classes and objects) isn´t rocket science, either. Java
is also a good place to start. It´s cleaner than C++, with more clarity and a better foundation; But it´s not (yet) as easily turned into a usable application as with C. But it´s getting there. And Java is immediately portable by design. (Provided you´ve got the runtime environment on your machine, which isn´t a problem anymore.
Corporate e-Business is getting more and more based on java server applications.
I wouldn´t use BASIC
unless I´m forced to...
BASIC programs end in a mess by default. It´s very hard to keep BASIC programs maintainable. And BASIC isn´t standardized. There are hundreds of mutually incompatible dialects; Your experience with one of them can be more of a burden than an asset. Assembler
is also a very good start, but not everybody would like to do it this way (in fact, it scares most people like hell
). It will give you a lot more insight, but it´s only for real men
And for most applications, you won´t have to dive quite that deep. But it´s still indispensable for time-critical components, because even a good C compiler will give you at most
half the speed of a decent assembly implementation. But that doesn´t matter all that much unless you´re planning to write real-time video CoDecs.
And, of course, assembly language isn´t very portable. COBOL
: As far as I know, it´s slowly dying out, even among bank and insurance IT departments... ADA
: Nice to hear it´s still around (it´s not really new anymore). But it´s a very small niche - even if an interesting one. And compilers aren´t exactly cheap.
But whatever language you might choose in the end:
- Document your code!!!! Not just for anybody else, but especially for your own good! You will want to understand your own stuff even next year! (Famous last words: "The code is obvious!" No, it isn´t! )
- The debugger is your friend! Tracing your own code is the best and fastest way to find out why you intended A and it gives you B.
- Don´t be afraid to experiment! Unless you´re fiddling with your operating system´s harddisk formatting routines it´s usually a good idea to make a few experiments if you´ve got trouble understanding something in a book.
- While I´m at it: A good book can help a lot! The compiler documentation won´t get you far, in most cases. Even better if you´ve got somebody you can ask.
Good luck, and have fun