Tag Info

1

Here are some findings after I investigated a bit. Header/tag information In the case of the tag or header information that are in the form :Identifier:, there does not exist a definite rule. In fact, after searching the whole AddOns directory, it turns out that some packages use Author while others use Authors. The same is true for Example/Examples, ...

2

I'm not aware of a definitive guide. Something towards what is possible is at Stack Exchange which I use from a button to create a skeletons of notebooks & packages. From memory I was inspired by the report generation procedures which were introduced at the time. Of course, YMMV.

1

No "real" answer, but a deeper analysis into the behavior you experienced: file = "original.m"; fileEnc = "enc.m"; (* alphabet for password: [0-9a-zA-Z] *) alphabet=Sort[CharacterRange @@@ {{"a", "z"}, {"A", "Z"}, {"0", "9"}}//Flatten, ToCharacterCode@#1 < ToCharacterCode@#2&]; (* checking and recording success of decryption together ...

6

To long for a comment: I think there are multiple typos (I hope) in docs for Get. This will work Get["Test", Path -> {NotebookDirectory[]}] even without SetDirectory and this will work automatically too: SetDirectory @ NotebookDirectory[]; << Test So the difference is in  More accurate in description is tutorial/FilesForPackages ...

0

The comment given by Szabolcs works as an answer. He suggested using: Get["D:\\at_work\\mathematica\\programming_maeder\\ComplexMap.m"] He also made it clear that one is not allowed to use an underscore in a Context name. The comment given by george2079 also works as an answer. He suggested using: Get["ComplexMap", Path -> ...

0

If you test the code above, i.e. run mySetVar[t] it works correctly (i.e. var is set to 20). The problem is actually one of "Definition" rather than SetDelayed. Definition is a weird function that simply prints some info to the screen. In this case, it gets it wrong, i.e. there is a bug in Definition. As a work around, if you want authoritative ...

5

It appears that Mathematica is generating invalid C code, which is worth reporting to support even if it turns out to be caused by unsupported input. That said, nesting compiled functions like this usually leads to performance degradations because the nested function will trigger a callback to the main evaluation loop. In[10]:= << ...

3

Upon opening you can change the stylesheet and remove the docked cell: SetOptions[EvaluationNotebook[], DockedCells -> {},StyleDefinitions -> "Default.nb"] Then if you want to change the "Code" styles to something else, possibly "Input", do this: NotebookFind[EvaluationNotebook[], "Code", All, CellStyle] ...

3

Here is one way. Using the parseString function from this answer of Mr.Wizard, the following will create a notebook with an entire package's code being placed in a single Code - style cell: parseString[s_String, prep : (True | False) : True] := FrontEndExecute[UndocumentedTestFEParserPacket[s, prep]] ClearAll[openPackage]; ...

Top 50 recent answers are included