Timeline for Function with custom Options and modified Options for built-in Symbols
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2015 at 13:45 | comment | added | Santiago | Ok thanks! At the moment I don't have much time, but on the weekend I'll try to do the most suitable MWE that I can come up with. | |
| Mar 16, 2015 at 23:04 | comment | added | Mr.Wizard | @Santi (1) To escape code that includes a back-tick you must wrap it in double back-ticks. (2) I suggest you post a new question with a minimal working example of both packages A and B. To debug the problem I would need to start by recreating these myself and it would be better that it come from you so that it is genuinely representative. | |
| Mar 16, 2015 at 14:56 | comment | added | Santiago | I also declared the options for my custom "Grid" function in package A, using: option1::usage="..." before trhe Private context. That means that packageB can see the options of the function in package A. | |
| Mar 16, 2015 at 14:34 | comment | added | Santiago | I can't format very well the output here, but yes, I am not forgetting any "`" or something | |
| Mar 16, 2015 at 14:33 | comment | added | Santiago |
@Wizard yes I am using this: ` BeginPackage["PackageB", {"PackageA"}] `
|
|
| Mar 16, 2015 at 14:30 | comment | added | Mr.Wizard |
@Santi Are you including package A in the BeginPackage expression in package B?
|
|
| Mar 16, 2015 at 14:20 | comment | added | Santiago | Hi Mr.Wizard and @Leonid, instead of a separate question I will write it as a comment, unless you consider it is better not to. I have been using the method of this answer succesfully with buil-tin functions. But now imagine that Grid in the above example is one functon I wrote in package A and myGrid is a function I wrote in package B. Then this method returns an error message, that an option is unknown. When I evaluate myGrid twice then it works. You have an idea why? | |
| Mar 6, 2013 at 23:14 | vote | accept | Markus Roellig | ||
| Mar 1, 2013 at 19:49 | comment | added | Leonid Shifrin | Ok, you are right. My fault, then. In some sense, the placement is right in the docs. | |
| Mar 1, 2013 at 19:32 | comment | added | Mr.Wizard | @Leonid It's right on that page, under Details -- I can see how that seems hidden. | |
| Mar 1, 2013 at 19:30 | comment | added | Leonid Shifrin | This does indeed, but this is not what I see in the V9 documentation, where only list of rules is mentioned. I will try to remember to ask why there was such a change. | |
| Mar 1, 2013 at 18:10 | comment | added | Mr.Wizard | @Leonid I put a copy of a line from the documentation at the top of my post. Does it not describe this use? | |
| Mar 1, 2013 at 17:49 | comment | added | Leonid Shifrin |
This particular form is not documented (list of functions inside OptionsPattern[]). I wasn't aware of it.
|
|
| Mar 1, 2013 at 17:43 | history | edited | Mr.Wizard | CC BY-SA 3.0 |
add documentation reference
|
| Mar 1, 2013 at 17:39 | comment | added | Mr.Wizard | @Leonid I had no idea this was esoteric. :-) | |
| Mar 1, 2013 at 17:36 | comment | added | Leonid Shifrin | This is pretty cool, +1. | |
| Mar 1, 2013 at 16:08 | history | answered | Mr.Wizard | CC BY-SA 3.0 |