Comment Re:Scripting language du jour (Score 1) 547
Perl (5/6)?
Perl (5/6)?
Almost every tech site on the planet has that story and you pick the National Enquirer styled tech site?
Tsk, tsk. The submitter should be ashamed. The Register has shown itself to be completely untrustworthy.
The British rag The Daily Mail has been coming up in Google News with the above linked story.
It is incredibly faulty; it's propaganda. The headline screams "The terrible truth about cannabis: Expert's devastating 20-year study finally demolishes claims that smoking pot is harmless".
There is no other dimension. They are two related but different languages, so treat them like e.g. C# and Java.
Delphi can actually compile C++ code.
You're thinking about C++Builder. They are two different products, even if they happen to be owned by the same company, and have some compatibility in terms of using libraries across two languages.
It's mostly just you.
With respect to different versions not being backwards compatible, it's more of a branding issue. There are two languages. One is Python 2, the other is Python 3. Within each of those, there's backwards compatibility, but between them, they're not compatible in general (though with some care it's possible to write code that works in both, and with some more care it'll even do the same thing - but you'd best leave that to library writers...). For your own project, pick one and stick to it. For other people's code, you might need both 2 and 3, but you should only need one version of each.
Unlike Java, no-one is trying to sell Python as "the language to rule them all", though, and the performance makes it clear that you want other stuff for some things. Heck, even the official docs have that huge section on writing C extensions.
Why would you need that kind of stuff built into the language, though? With sufficiently flexible syntax, the libraries should do the trick.
And, FWIW, I hear a lot about people switching from R to Python (with the corresponding libraries, naturally - including an R bridge for gradual migration) lately.
Operator overloading is not different from functions at all - operators are just functions with fancy names. And a programmer can just as well define a function that has "multiply" as a name, but does something else entirely, as he can define operator * that does something else entirely. These two are identical in all aspects. The only reason why operators were historically not redefinable is precedent, and it doesn't have any reasoning behind it.
Intel CPUs are not defective, they just act that way. -- Henry Spencer