Timeline for How to prevent arguments UpValues from being used in selective functions
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8, 2019 at 18:20 | vote | accept | void life | ||
| Jan 8, 2019 at 15:14 | comment | added | void life | That's neat, it seems like the most elegant solution right now. I'm using Mathematica 11.3 so I can take advantage of it. | |
| Jan 8, 2019 at 9:06 | history | edited | Mr.Wizard | CC BY-SA 4.0 |
deleted 1 character in body
|
| Jan 8, 2019 at 6:23 | comment | added | Mr.Wizard | @void If you are using Mathematica 10.4 or later please see my update and tell me if it is more to your liking. | |
| Jan 8, 2019 at 6:23 | history | edited | Mr.Wizard | CC BY-SA 4.0 |
added 365 characters in body
|
| Jan 8, 2019 at 1:14 | comment | added | void life |
Thank you for the answer. While this does simply many things with regards to handling (I don't have to mess with upvalues anymore), I don't think it is particularly better than my 2nd approach. The more complicated key addressing will produce more clutter or clutter scoping blocks everywhere than just creating the upvalue definitions once off. Plus when I have many of these atomData 'types' doing With[{a1 = aa1[[1]], a2 = aa2[[1]] ...] gets cumbersome. Any thoughts on the PS. part of my question? - if I should continue with the OO paradigm
|
|
| Jan 8, 2019 at 0:10 | history | edited | Mr.Wizard | CC BY-SA 4.0 |
fix
|
| Jan 8, 2019 at 0:05 | history | answered | Mr.Wizard | CC BY-SA 4.0 |