Quote from a past solution explaining the C-style Perl for-loop used:
And yes, we could have used the Perl shorthand here and incremented our counter like this:
$total++;
Right... | [reply] [d/l] |
Pity. Despite low Perl skill level of judges, I have learned a few "tricks" from previous edition. | [reply] |
It's Microsoft. What else would you expect? My only surprise is they aren't pushing IronPython (yet). | [reply] |
| [reply] |
I hope your tongue is in your cheek.
MS has allowed scripting for a very long time and has provided mechanisms for it for a very long time as well. It was simplistic, underpowered, and in some ways outright crippled, but even early versions of DOS could be scripted out of the box. Later versions of DOS included QBasic, which was a trimmed-down version of QuickBasic.
Some very complex programs have been written in QB (up to and including Wolfenstein-class games). Some fairly complex ones were written in DOS batch files with the help of additional utilities. I wrote a number of utility programs which used the two together.
Windows has had access to most of the DOS batch language, the Windows Scripting Host, and MS has included Perl as part of their resource kit for Windows. They provide the C# runtime without royalties, paid for much of the development for ActiveState's Perl distro, and provide test environments to CPAN developers.
MS prefers to make money selling development tools. Windows doesn't have the sort of gratis support for programmers that Linux or the BSDs do. It's going a bit far to say that Microsoft and scripting are contradictory, though.
| [reply] |
| [reply] |
I guess Perl just outclasses the others listed, so it's not fair to put them in the same game. You don't put a Formula 1 race car in a stock-car race, right? | [reply] |
2012 and still writing effective hta (html+css+vbscript) applications... yeah, that's right, i said vbscript...
i would prefer perl, but, vbscript runs native on pretty much all versions of MS... so, i save the perl for linux/unix.
| [reply] |