Timeline for How to verbalise code in Mathematica?
Current License: CC BY-SA 4.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 15, 2021 at 16:24 | comment | added | Roman | @MichaelE2 please free to add yours, let's make an inclusive list of alternatives! | |
| Mar 15, 2021 at 16:00 | comment | added | Michael E2 |
I think until a universal convention manages to emerge, there will be differences of personal taste. Personally, I prefer to keep the names I use close to the command names, e.g. read x /. y as "x replace-all y" or "x ReplaceAll y". Less cognitive load, reinforces learning the names of the functions. Doesn't work for syntax that are not commands, e.g. x // y for which your "x then y" is good. I'm sure if I wrote out my verbals habits, some folks would dislike some of my suggestions. :)
|
|
| Mar 15, 2021 at 7:44 | history | edited | Roman | CC BY-SA 4.0 |
added 132 characters in body
|
| Oct 20, 2019 at 16:44 | history | edited | Roman | CC BY-SA 4.0 |
added 132 characters in body
|
| Oct 20, 2019 at 7:52 | history | edited | Roman | CC BY-SA 4.0 |
added 264 characters in body
|
| Jul 1, 2019 at 17:01 | history | edited | Roman | CC BY-SA 4.0 |
added 528 characters in body
|
| Jul 1, 2019 at 13:30 | history | edited | Roman | CC BY-SA 4.0 |
edited body
|
| Apr 27, 2019 at 21:51 | history | edited | Roman | CC BY-SA 4.0 |
edited body
|
| Apr 27, 2019 at 21:37 | comment | added | Roman |
Yes @BobUeland I had extrapolated your earlier comment to include x_y as "anything of type y, call it x".
|
|
| Apr 27, 2019 at 19:39 | comment | added | Bob Ueland | Do you have _h in your table? It represents any expression having the h as its head. For instance f[x_Integer] :=... defines a function that takes any integer as a parameter. I would pronounce x_Integer as "any integer call it x". | |
| Apr 27, 2019 at 18:34 | comment | added | Roman | @bobthechemist please feel free to add the way you would pronounce things to the list! I teach Mathematica too and would be keen to have a consistent list. | |
| Apr 27, 2019 at 18:31 | history | edited | Roman | CC BY-SA 4.0 |
added 17 characters in body
|
| Apr 27, 2019 at 18:05 | history | edited | Roman | CC BY-SA 4.0 |
edited body
|
| Apr 27, 2019 at 18:00 | history | edited | Roman | CC BY-SA 4.0 |
added 132 characters in body
|
| Apr 27, 2019 at 17:47 | history | edited | Roman | CC BY-SA 4.0 |
added 490 characters in body
|
| Apr 27, 2019 at 17:37 | history | edited | Roman | CC BY-SA 4.0 |
added 490 characters in body
|
| Apr 27, 2019 at 17:25 | comment | added | bobthechemist | As I spend a fair amount of time teaching Mathematica to students who have never done programming, having a list of terms to use for the language's typography - if only to be self-consistent - is very helpful. | |
| Apr 27, 2019 at 16:53 | vote | accept | Bob Ueland | ||
| Apr 27, 2019 at 16:52 | comment | added | Bob Ueland | thank you for a nice beginning. I often pronounce x_ as "anything, call it x". I guess you could pronounce x__ as "any sequence, call it x". And maybe you could pronounce x___ as "any sequence including empty, call it x". | |
| Apr 27, 2019 at 16:20 | history | edited | Roman | CC BY-SA 4.0 |
added 32 characters in body
|
| Apr 27, 2019 at 15:57 | history | answered | Roman | CC BY-SA 4.0 |