Search Results

Use Text in Graphics. This page, and the ones linked under Tutorial (top right corner) explain how to type math. Here's one way, keystroke by keystroke: ", a, ", ←, shift+←, control+shift+T, ←, con …

In[2]:= ParallelDo[Print[a], {4}] (kernel 4) 1 (kernel 3) 1 (kernel 2) 1 (kernel 1) 1 a is now recorded in the list of distributed symbols. … In[3]:= Parallel`Developer`$DistributedDefinitions Out[3]= {Hold[a]} Setting a as shared removes it from the list of distributed symbols to prevent bad interactions between the sharing and distribution …

Unique will do precisely this. Try for example Unique[x], which returns a symbol with a name similar to x$123. Here I should mention the Temporary attribute as well, which, when associated with a sy …

BeginPackage["Foo`"]; Unprotect["Foo`*"]; (* list all symbols meant for export, including any symbols used as options only *) Begin["`Private`"]; (* package code *) With[{syms = Names["Foo`*"]} …

You cannot clear it, because \[ImaginaryJ] does not have a definition. \[ImaginaryJ] does not transform to I through the normal evaluation procedure. Instead, it is directly parsed as the imaginary un …

Don't think about these things in terms of "scope", as that will lead to confusion. Mathematica does not (usually) use "scope" in the way you may be familiar with from other languages. In particular, …

Please read here first on how Mathematica searches contexts for symbols. In short, $Context tells it where to create symbols. It's for creation, not for lookup. … $ContextPath tells it where to look for symbols but doesn't affect symbol creation. If the symbol is not found in any of the $ContextPath contexts, Mathematica proceeds to create it in $Context. …

You already have a palette for a great variety of symbols used in math. Just go to Palettes -> Special Symbols. The palette contains the $\mathfrak{A}$ symbol as well. …

foo`bar (* foo`bar *) ToString[foo`bar] (* "foo`bar" *) SymbolName[foo`bar] (* "bar" *) Warning: Converting between symbols and strings requires great care, especially when different contexts are … Robust code will not normally convert between strings and symbols. …

The reason why the subsequent evaluation of the second code block doesn't trigger the warning is that it doesn't create any new symbols. Both A`n and B`n have already been created. … If you are writing a package, you should only place those symbols into the package context which are meant to be directly used by the package's users. Above, n is not such a symbol. …

In this case, I chose to include a few extra checks, as well as unprotect/protect symbols. Notice, however, that only System` context symbols appear in this file. … A simple way is With[{symbols = Names["MyPack`*"]}, SetAttributes[symbols, {Protected, ReadProtected}] ] However, this would create Global`symbols. …

If you literally have FindSym[x_] := Position[x, mySym] in your package, then this mySym is probably created in PA`Private` (depending on your package setup). PA`Private`mySym is distinct from Glob …

Like Leonid, I also prefer capitalized public package symbols. … accidental conflicts with built-in symbols or package symbols. …

I usually use ToExpression["symbol", InputForm, ValueQ] ToExpression will wrap the result in its 3rd argument before evaluating it. Generally, all functions that extract parts (Extract, Level, …

This is not the case if there's a conflict with System` symbols, as that context is still active and visible to package B during load time. …