Anonymous user
User talk:Horst.h: Difference between revisions
changed === to ==, added a section header to the first topic to properly place the table-of-contents (TOC), and added two talk topics.
No edit summary |
(changed === to ==, added a section header to the first topic to properly place the table-of-contents (TOC), and added two talk topics.) |
||
Line 1:
==timings on RC==
Hi, I note that in one of your examples you sprinkle timings. On RC we tend not to get too involved in mentioning runtimes unless it is exceptionally slow. It is best to restrict timings to maybe comparative timings between two algorithms in the same language, and only where necessary: "This new algorithm cut the run time from X hours to only Y minutes" kind of thing. Actual run times will be hard to duplicate by anyone else, but th scaling in run times might be achieved. The RC emphasis is on idiomatic code rather than the absolute fastest code. Most examples will not take hours to run in most programming languages, and most examples don't need timings.
Thanks for your examples :-)<br>--[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 23:09, 12 December 2018 (UTC)
You have obviously gone to great lengths to produce a fast version of this using Free Pascal, which caused me to look up what it is and found it interesting that it is a reincarnation and modernized version of Turbo Pascal/Delphi (most of the current contributors seem to have been not more than about 10 years old when Turbo Pascal first appeared!). Although I used Turbo Pascal commercially in about 1983 and later learned Delphi, it didn't cause me to want to abandon my current stable of more modern languages to take Pascal up again. But your taste seems to differ.
Line 33 ⟶ 35:
: It's been a "blast from the past" for me to re-visit Pascal after all these years in order to write this benchmark, but it has also made me realize how far language design has moved on since Turbo Pascal days when we used to rave about it: when compared to a modern language like Kotlin, or Nim, or with modern functional languages like Haskell or even more F#, there is just no going back for me as it feels "clunky". Verbosity in declaring var's separately from the code using them, no type inference whatsoever, begin/end blocks, etc. etc. Even Julia is better, although I don't like dynamic typing there are ways to get around it with some effort.--[[User:GordonBGood|GordonBGood]] ([[User talk:GordonBGood|talk]]) 04:43, 8 January 2019 (UTC)
Thanks/wow --[[User:Petelomax|Pete Lomax]] ([[User talk:Petelomax|talk]]) 12:45, 26 June 2019 (UTC)
==signing the adding of text in discussions==
When adding (your) text to topics on discussion pages, please sign (appended at the end of your additions) with:
<br>
:::: <big><big><big> <nowiki> -- ~~~~ </nowiki> </big></big></big>
That is, two minus signs (or whatever), with four tildes (<b>~</b>). The latter adds your ID (name), and the UTC date and time. (There are other formats you can use.)
It saves (for all others) the bother of looking up who did what in the ''history'' page. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 22:08, 15 August 2019 (UTC)
==Brazilian numbers speed up==
Thanks for your hints on speeding up the calculations of Brazilian numbers.
Because I looked up the history incorrectly, I attributed the hint to the wrong person. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 22:08, 15 August 2019 (UTC)
| |||