what language should i learn??

[smithmiller6]

hi
i want to spend my time to learning Programming. i know some of C++, HTML, PHP, VB

but i want to learn Programming language who use full for me more,

can any one help me to give idia how can i make software like that

Auto article submit software
Auto bookmarking software
Auto directory submit
etc..
looking for information what language should i learn for making that type of softwares.

any information is very useful for me.

[brokenbylaw]

I prefer C++,C and perl/python c++ and C can do just about anything so i would go for that, if the learning curve isn't too high

[Firebird_38]

Go with Delphi/Pascal.

It's much easier to read than C and C++. It also produces the same quality/speed programs, but you can make it faster and it's easier to use, less error prone.
C and C++ tend to magnify your mistakes. Also, Delphi manages the memory for strings for you, whereas C and C++ don't You must allocate every string and free it, or provide fixed string buffers (and create security holes and bugs known as buffer overruns).

In general, Pascal has better compile time type checking, which means it does a better job of finding mistakes you make. C and C++ allow you to do things that get you in trouble. You can still do all those tings in Pascal, but you have to explicitly write code to mess up on purpose.

ASlo, Pascal/Delphi uses Units. Units have theirt own namespace, which means you can use identifiers (names) used in other units and not have a name clash. Since C and C++ basically create one big file for your whole program, names must be unique throughout all libraries and program code. This in turn means long names, such as having to prefix all you functions from a library with libraryname like in article_submitarticle and article_createnewarticle. Also, units are compiled independently from each other, even though C has obj/lib files.

C and C++ have macros, though, something that's completely absent in Pascal and Delphi. Macros can however be troublesome to work with and are also error prone. Just use functions in Delphi.

Delphi also has procedures, something C and C++ can only emulate with void functions.

You can also use C code in Delphi, by linking the obj file. The other way around doesn't work as well, unless you use Borland C/C++, which has complete built-in support.

Lastly, Delphi has a very nice Rapid Application Development framework known as the VCL (Visual Component Library) that makes it easy to connect to databases and the internet, and makes it easy to setup your GUI.

Enjoy learning.

[WingedPanther]

Go with Delphi/Pascal.

or Lazarus

It's much easier to read than C and C++. It also produces the same quality/speed programs, but you can make it faster and it's easier to use, less error prone.

C++ has excellent methods to help you avoid errors. Syntax issues are a matter of taste. Delphi is more verbose, but not necessarily easier to read.

C and C++ tend to magnify your mistakes. Also, Delphi manages the memory for strings for you, whereas C and C++ don't You must allocate every string and free it, or provide fixed string buffers (and create security holes and bugs known as buffer overruns).

Umm... and then you lost me. C++ std::string manages memory for you just fine. I agree that C can be painful, however.

In general, Pascal has better compile time type checking, which means it does a better job of finding mistakes you make. C and C++ allow you to do things that get you in trouble. You can still do all those tings in Pascal, but you have to explicitly write code to mess up on purpose.

Again, huh? I suspect you haven't worked much with C++, though I will grant what you said about C.

ASlo, Pascal/Delphi uses Units. Units have theirt own namespace, which means you can use identifiers (names) used in other units and not have a name clash. Since C and C++ basically create one big file for your whole program, names must be unique throughout all libraries and program code. This in turn means long names, such as having to prefix all you functions from a library with libraryname like in article_submitarticle and article_createnewarticle. Also, units are compiled independently from each other, even though C has obj/lib files.

C++ also has namespaces. Also, you should NEVER create a large project as one big file in ANY language. Most compilers make multiple object files and then link them. Not what you described at all.

C and C++ have macros, though, something that's completely absent in Pascal and Delphi. Macros can however be troublesome to work with and are also error prone. Just use functions in Delphi.

C++ makes macros basically unnecessary.

Delphi also has procedures, something C and C++ can only emulate with void functions.

C++ has void functions, something Delphi can only emulate with procedures. They're the same concept.

You can also use C code in Delphi, by linking the obj file. The other way around doesn't work as well, unless you use Borland C/C++, which has complete built-in support.

Lastly, Delphi has a very nice Rapid Application Development framework known as the VCL (Visual Component Library) that makes it easy to connect to databases and the internet, and makes it easy to setup your GUI.

C++ has several RAD developments, depending on the GUI library being used. Borland C++, for example, has a nice one

Enjoy learning.

Lazarus/Delphi is a good choice, don't get me wrong, but most of the arguments are not valid.

[Firebird_38]

In Units, the namespace is implicit, and C/C++ needs separate header files, whereas the "header" is the interface section in a unit. Keeps them handily together .

About functions: They're a concept from mathematics. They're supposed to produce an output based on the parameters. Think Sin(10). A procedure is simply a way of doing things. Of course, programming has changed the meaning of these concepts a bit. For instance, functions in programming can use other info than just the parameters (for instance, global variables). The word "procedure" however, is conceptually much more accurate than "a function that doesn't return anything", because the very word "function" comes from something that returns something, or even better "stands for something", not nothing. Besides, "void function x()" is more verbose than "procedure x;", which is another thing C likes to mess with: function calls need parentheses, even if no parameters are passed. The silliness . C has no concept of passing by reference other than using pointers. Pointers are horrible for beginners. They are the main cause of errors. Passing a parameter by reference by using "var" is less error prone, I'd say.
As far as the "one file" thing I mentioned: C header files are included, as in "injected" into your code. All the identifiers from the header get injected into your code, which I believe would be the global namespace. And further, header files and obj files don't need to be the same version. I can easily modify the header file and still use the same obj file. If I change a function definition in the header, this would lead to crashes. Units have no such problem, as they are always compiled as one. Of course, the object files get linked in, though, and that means it's indeed not one file. The shared header identifiers, however get injected into the global namespace, though, which is the point I was making. Units stop this problem, because you can re-use the same identifiers (even interface ones) and still have them available in the global namespace. When needed, you can prefix the unit name to select which one you want.

In short, I believe Pascal is better on a conceptual basis. However, they can do the same things, and as such both can produce software that is equally powerful. Both are compiled to machine code.

I did want to mention, though that ANSI C (not C++) has something that Pascal lacks. This is the ability to be compiled on almost all platforms. Be it Linux, Mac, Windows, your cell phone and PDA, your XBOX or PlayStation, C will compile. The same cannot be said for Pascal, even though it is possible to make compilers for Pascal on all platforms, this isn't currently so. However, just as there is an ANSI C, there's also an ANSI Pascal (ANSI-ISO Standard Pascal, ISO 7185), which is a platform-independant standard, that comes, like C, without powerful libraries.

Something I forgot to mention: C, C++, and a bunch of other languages are cASe SenSitiVE, which is very annoying. Like "DestroySystem" means somthing else than "Destroysystem". Why should it? Sounds the same to me. I hope you backed up!

C is the best

But, Delphi is the easiest (without sacrificing speed). BASIC is very basic. .NET is compiled to bytecode. Slow, slow, slow. (That's why you need to upgrade your PC. Programs don't get better, they just get slower because of new technologies, bloat, and, of course Microsoft. Thank you, Microsoft.)

I love it when I'm right. Too bad I'm wrong sometimes . lol



PHP makes one single file (well, it may not physically do this, but it might as well, except it would work a bit slower, memory wise).

That's great, isn't it?



If you just want to make "certain software" as mentioned, I would go with Delphi.

If you want to learn how to program to make stuff forever, go with C or a variant.

The reason is, you will lock in your abilities to the Windows platform with Delphi. You shouldn't do this. You'll regret it. Learn the hard thing: C, C++, C#. C(variant) programmers call it "a real programming language" and think of themselves as hardcore (No, not all of them, a lot of them, though, and if you C person want to protest, I didn't mean you, someone else. Don't protest.)

By going with Delphi, you'll scar yourself with the mark "softie" for life. If you want to be a real nerd,you'll have to write cryptic code as in

 for (n--;n*n!=12;++n){j+=(--i%3==2)%12}

What does it mean? Probably nothing. But it'll compile . And if the compiler understands it, so should you.

For real, though, C and its variants are more accepted, more widespread, more compatible and more "hardcore". I'd go with Delphi, forget XBox for now . But you should go with C++ or something. The reason is that you want to be "available" and "flexible", not conceptually correct.

C++ would be the lesser of the evils, but Delphi will get you going quicker. In other words, C++ will keep you going forever, but you may end up at a roadblock with Delphi, and end up having to learn C after all.

Good luck learning C and beware of the pointers(*), the pointer references, the pointer to pointers (**), the loose typing (**t()), and the death traps (Exception 0x0D)

[QuackWare]

It depends if you want to learn a web based (scripting) language or a language used more often for desktop applications. I prefer C# because it is easy to learn and still creates some powerful applications, also it is very similar to Java if you want to switch over to a Linux or Mac programming environment.

For web based I would suggest python or php, whichever seems to suit your taste.

[Red_Shadow]

Programs that have script-like tasks (copy things, network scripting, etc), all the things you mentioned actually, I find are easiest done in Perl. Perl allows you to do whatever you want, so you can cook up a solution for minor programs very quickly.

For overall programming, I prefer Lisp, because it lets you write effective code in very little time, once you "get" it.