Timeline for What is the most convenient way to read definitions of in-memory symbols when we don't have the source files? (Spelunking tools)
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 12, 2019 at 23:34 | comment | added | berniethejet | +1. Could it print something like 'there are 35000 DownValues and 1 Attributes for 'Temp'' instead of 'Temp has too many definitions (35001) to display.'? | |
| Dec 27, 2016 at 23:35 | comment | added | b3m2a1 |
@QuantumDot it's possible to escape that behavior by setting Length to max out at 127 using Villegas-Gayley. PrintDefinitions will work fine then, although it seems in 11.0 the max has been changed to 256.
|
|
| Jun 15, 2016 at 10:29 | comment | added | Ronald Monson | Just stumbled onto this. Very handy. Hopefully will one day become part of a FE IDE ... | |
| May 30, 2016 at 9:37 | comment | added | QuantumDot |
What's the matter with printing more than 128 definitions? I can't do PrintDefinitions[ComplexAnalysis`BranchCuts] because it has 166 definitions. Would you kindly take away this limitation or maybe add an option "MaxDefinitions" that sets the threshold? thanks!
|
|
| Nov 26, 2015 at 15:22 | comment | added | István Zachar |
Thanks for the reply. BTW, I've found PrintDefinitions@NonlinearStateSpaceModel to crash the kernel after a flood of error messages. I assume the problem is not in PD but in some loose NSSM definitions evaluating prematurely?
|
|
| Aug 7, 2015 at 22:28 | comment | added | Taliesin Beynon |
@IstvánZachar that's just an oversight. You can use PrintDefinitions to patch Definitions, though that won't survive a kernel restart obviously.
|
|
| Aug 7, 2015 at 22:27 | comment | added | Taliesin Beynon | @SimonWoods cool, thanks for the inspiration! | |
| May 19, 2015 at 19:19 | comment | added | Simon Woods | I've only just seen this - awesome! It's really good to have something like this built in, many thanks. | |
| May 8, 2015 at 12:35 | comment | added | István Zachar |
Is it by design that (Print)Definitions omits formatting definitions like MakeBoxes[...]^:=... (e.g. in case of PrintDefinitions@EvaluationObject)? Is it because some dynamic formatting box could lead to problems when evaluated for printing? @Rolf Try ChartElementData: it has 1853 definitions.
|
|
| May 7, 2015 at 22:55 | comment | added | Murta |
@RolfMertig Dataset is one of these functions, with 189 definitions.
|
|
| Apr 2, 2015 at 18:46 | comment | added | Taliesin Beynon | @RolfMertig more that before we had associations, people would use symbols as a key-value store via their downvalues... and there might be thousands of definitions on such symbols. | |
| Apr 2, 2015 at 17:39 | comment | added | Rolf Mertig | Fantastic! This looks really useful. Is there really an internal function with more than 128 definitions? | |
| Apr 2, 2015 at 16:59 | history | edited | Taliesin Beynon | CC BY-SA 3.0 |
Mention color coding and OwnValues.
|
| Apr 2, 2015 at 16:44 | history | answered | Taliesin Beynon | CC BY-SA 3.0 |