Talk:Antihydra: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 5: | Line 5: | ||
: I'll change the article to use the modified variable names. You are referring to *h* instead of *b* and *c* instead of *a*, right? [[User:MrSolis|MrSolis]] ([[User:MrSolis|talk]]) 15:02, 30 April 2025 (UTC) | : I'll change the article to use the modified variable names. You are referring to *h* instead of *b* and *c* instead of *a*, right? [[User:MrSolis|MrSolis]] ([[User:MrSolis|talk]]) 15:02, 30 April 2025 (UTC) | ||
:: Yes, a->c and b->h in this article. h being the always increasing current hydra function value. It would probably also be a good idea to agree on a standard order of these two (h first?) [[User:Coda|Coda]] ([[User talk:Coda|talk]]) 15:07, 30 April 2025 (UTC) | |||
:::I chose the order I did simply bcuz its the same order as in the config but if u think swapping it truly helps, then idm doing it but thats yr call [[User:MrSolis|MrSolis]] ([[User:MrSolis|talk]]) 15:49, 30 April 2025 (UTC) |
Latest revision as of 15:49, 30 April 2025
Variable Naming Conventions
I noticed that the usage of the variables 'a' and 'b' in this article are opposite to how they are defined in other sources. Can we modify this article to make it more consistent? Peacemaker II (talk) 00:36, 30 April 2025 (UTC)
Agreeing to the above that renaming the variables in this article would align it to most other sources and also proposing naming these variables h (*h*ydra) and c ((*c*ollatz-like) *c*ondition *c*ounter) instead for easier remembering Coda (talk) 00:57, 30 April 2025 (UTC)
- I'll change the article to use the modified variable names. You are referring to *h* instead of *b* and *c* instead of *a*, right? MrSolis (talk) 15:02, 30 April 2025 (UTC)