Skip to content

Commit

Permalink
Delete misleading section on "module file path"
Browse files Browse the repository at this point in the history
This was never accurate and doesn't really belong in the modules
section since modules have nothing to do with the load path other
than the fact that packages define a module and packages the load
path affects what packages can be loaded.
  • Loading branch information
StefanKarpinski committed Feb 8, 2019
1 parent 2550925 commit 6a4ccf3
Showing 1 changed file with 0 additions and 13 deletions.
13 changes: 0 additions & 13 deletions doc/src/manual/modules.md
Original file line number Diff line number Diff line change
Expand Up @@ -183,19 +183,6 @@ look for `Utils` in `Parent`'s enclosing module rather than in `Parent` itself.

Note that relative-import qualifiers are only valid in `using` and `import` statements.

### Module file paths

The global variable [`LOAD_PATH`](@ref) contains the directories Julia searches for modules when calling
`require`. It can be extended using [`push!`](@ref):

```julia
push!(LOAD_PATH, "/Path/To/My/Module/")
```

Putting this statement in the file `~/.julia/config/startup.jl` will extend [`LOAD_PATH`](@ref) on
every Julia startup. Alternatively, the module load path can be extended by defining the environment
variable `JULIA_LOAD_PATH`.

### Namespace miscellanea

If a name is qualified (e.g. `Base.sin`), then it can be accessed even if it is not exported.
Expand Down

0 comments on commit 6a4ccf3

Please sign in to comment.