You may all know about String concatenation in Delphi, but do you know about the implicit String variables the compiler may create for you?
Along with the implicit variables come implicit exception frames, and a whole lot of hidden stack juggling, which can quickly become hidden complexity bottlenecks.
I’ve closed the mini-pool, below are the results, obtained after 500 respondents, as well as some other stats not obviously evident from the poll results (as it was a multi-choice poll).*
They’re of course only relevant as the measurement to the audience of this site.
…or at Work if your prefer.
This is a small poll to gauge the audience of this site,, try to answer about the environments you use for production, not for experimenting, testing or fiddling.
If you use several version, feel free to check as many entries as you feel are relevant.
Work and processing classes are typically short-lived, created to perform one form of processing or another then freed. They can be simple collections, handle I/O of one kind of another, perform computations, pattern matching, etc.
When they’re used for simple workloads, their short-lived temporary nature can sometimes become a performance problem.
Worst thing in popularity is not being considered, or found.
Looks like TIOBE is not alone in differentiating Delphi and Pascal, other popularity indexes share the same issue:
More indexes I looked at didn’t show the “runners up”, only the top 5 or top 10, but they may as well have differentiated.
For lang-index, merging Pascal (rank 11) and Delphi (24), would be enough to reach rank 10, ahead of Ruby, just shy of Perl.