Talk:Chowla numbers: Difference between revisions

m
→‎Large computations: corrected a typo. away --> a way
m (→‎Large computations: corrected a typo. away --> a way)
 
(2 intermediate revisions by 2 users not shown)
Line 24:
: Do we really need to agree on this kind of thing ? Optional seems more than good enough [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 12:24, 11 March 2019 (UTC)
:: +1 for that. See below. If the language supports locales for numbers then OK. Writing a subroutine putting commas every 3 digits in an Anglophobe interpretation of appropriate seems worse than pointless almost stupid.--[[User:Nigel Galloway|Nigel Galloway]] ([[User talk:Nigel Galloway|talk]]) 15:50, 11 March 2019 (UTC)
:::Agreed. Tasks should focus on one specific problem. If adding comma is a recurring theme, then make it a task and if you really feel it should appear everywhere, at least make it optional. Besides, not all languagescountries use commas, in France at least the thousand separator is a space : much better to leave such details in a separate task. And while we are at it, adding non-breaking spaces everywhere in task descriptions should not be encouraged. [[User:Eoraptor|Eoraptor]] ([[User talk:Eoraptor|talk]]) 07:18, 13 March 2019 (UTC)
:::: I agree that the excessive specification on the formatting of task output takes the focus away from how different languages best solve a task. It makes perfect sense to me to move those formatting specifications to their own separate task. --[[User:Tikkanz|Tikkanz]] ([[User talk:Tikkanz|talk]]) 20:16, 14 March 2019 (UTC)
 
Line 73:
::Unfortunately I later learned that the sympy library holding divisors is pure Python, but it is well regarded so I used it rather than creating my own.
::Hi Gerard, I mainly program in interpreted Python but '''don't''' want the present limits to be lowered.
::It is good to have some tasks that stress some languages, but I was thinking of finding <strike>away</strike> a way for most of the slower mplementations to naturally use the same lowered lmits. In the Python example I tried to do something like that and used shorter runs to prove my code, but just left the longer runs to the end and left them running. Luckily for me, they eventually finished, after sometime! --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 21:49, 12 March 2019 (UTC)
 
::: Does Python use a non-interpreted "language" for its BIFs? &nbsp; (In particular, &nbsp; '''divisors'''.) &nbsp; &nbsp; The reason I ask is that I wrote a home-grown &nbsp; '''divisors''' &nbsp; REXX function that instead of finding the divisors, and then adding them (say, with a &nbsp; '''sum''' &nbsp; function), I modified a version of the &nbsp; '''divisors''' &nbsp; code to instead of creating a list of proper divisors, I had the function just add the divisors on-the-fly (eliminating the stand-alone summation part). &nbsp; I then further modified the function to be aware if the target is odd or even, and adjusted the &nbsp; '''do''' &nbsp; loop accordingly (along with the &nbsp; '''do''' &nbsp; loop increment); &nbsp; that doubled the speed (or halved the computation time, &nbsp; pot-tay-toe, pot-tah-toe). &nbsp; Essentially, I coded a &nbsp; '''sigma_proper_divisors''' &nbsp; function with the subtraction of unity as being built-in by starting the summation with zero instead of unity). &nbsp; &nbsp; &nbsp; Do you happen to know if Python's &nbsp; '''divisors''' &nbsp; BIF does that? &nbsp; I would suspect that it does. &nbsp; In any case, this is why I included several formulas/algorithms to calculate the &nbsp; '''chowla''' &nbsp; function so that programmers could choose the fastest (most efficient) algorithm. &nbsp; &nbsp; -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 23:00, 12 March 2019 (UTC)
Line 80:
 
::: I'm really impressed by the large perfect numbers computed with &nbsp; '''Visual Basic .NET''' &nbsp; using the Chowla function &nbsp; (2<sup>nd</sup> section, under &nbsp; '''more cowbell'''). &nbsp; That's going the extra mile, by gum. &nbsp; Going from roughly '''33 million''' to over '''8 billion''', &nbsp; and then to over '''137 billion''', &nbsp; and then to over '''2 quintillion'''. &nbsp; Was the computer smoking or losing its magic smoke? &nbsp; &nbsp; Kudos. &nbsp; &nbsp; -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 02:05, 13 March 2019 (UTC)
 
::::No magic cigarette, VB.NET benefits from .NET's JIT. It's not your grandma's VB6. [[User:Eoraptor|Eoraptor]] ([[User talk:Eoraptor|talk]]) 07:24, 13 March 2019 (UTC)
 
::::: Er, no. &nbsp; "Magic smoke" does not come from cigarettes. &nbsp; The term "magic smoke" is a running joke amongst electrical engineers, computer technicians and computer programmers. &nbsp; A electrical device operates until the magic smoke is released from it, at which point the component ceases to operate. Therefore, the magic smoke is a critical and essential part of the device's operation. &nbsp; &nbsp; -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 20:12, 19 March 2019 (UTC)
 
== Mistakenly posted discussion on the task page ==