From a3a615a4e080f4b8a79efc07dc9189ac4c22322f Mon Sep 17 00:00:00 2001 From: Michael Krabbe Borregaard Date: Tue, 14 Aug 2018 13:20:16 +0200 Subject: [PATCH 1/3] Remove mention of `reload` from the docs I believe `reload` has been deprecated. --- doc/src/manual/modules.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/doc/src/manual/modules.md b/doc/src/manual/modules.md index 74065606cc4e4..06c336168ddc9 100644 --- a/doc/src/manual/modules.md +++ b/doc/src/manual/modules.md @@ -232,13 +232,10 @@ For file dependencies, a change is determined by examining whether the modificat of each file loaded by `include` or added explicitly by `include_dependency` is unchanged, or equal to the modification time truncated to the nearest second (to accommodate systems that can't copy mtime with sub-second accuracy). It also takes into account whether the path to the file chosen -by the search logic in `require` matches the path that had created the precompile file. - -It also takes into account the set of dependencies already loaded into the current process and -won't recompile those modules, even if their files change or disappear, in order to avoid creating -incompatibilities between the running system and the precompile cache. If you want to have changes -to the source reflected in the running system, you should call `reload("Module")` on the module -you changed, and any module that depended on it in which you want to see the change reflected. +by the search logic in `require` matches the path that had created the precompile file. It also takes +into account the set of dependencies already loaded into the current process and won't recompile those +modules, even if their files change or disappear, in order to avoid creating incompatibilities between +the running system and the precompile cache. If you know that a module is *not* safe to precompile your module (for example, for one of the reasons described below), you should From e18655491ae80b4f14be98662c8a62b4f7e13354 Mon Sep 17 00:00:00 2001 From: Michael Krabbe Borregaard Date: Wed, 15 Aug 2018 10:29:58 +0200 Subject: [PATCH 2/3] Remove trailing whitespace --- doc/src/manual/modules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/manual/modules.md b/doc/src/manual/modules.md index 06c336168ddc9..654215ed5e03e 100644 --- a/doc/src/manual/modules.md +++ b/doc/src/manual/modules.md @@ -235,7 +235,7 @@ mtime with sub-second accuracy). It also takes into account whether the path to by the search logic in `require` matches the path that had created the precompile file. It also takes into account the set of dependencies already loaded into the current process and won't recompile those modules, even if their files change or disappear, in order to avoid creating incompatibilities between -the running system and the precompile cache. +the running system and the precompile cache. If you know that a module is *not* safe to precompile your module (for example, for one of the reasons described below), you should From 372033c39fef4a0d94134d368fc01c03e797332c Mon Sep 17 00:00:00 2001 From: Michael Krabbe Borregaard Date: Wed, 15 Aug 2018 10:50:54 +0200 Subject: [PATCH 3/3] really remove trailing whitespace --- doc/src/manual/modules.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/manual/modules.md b/doc/src/manual/modules.md index 654215ed5e03e..ef073cbe6db23 100644 --- a/doc/src/manual/modules.md +++ b/doc/src/manual/modules.md @@ -232,9 +232,9 @@ For file dependencies, a change is determined by examining whether the modificat of each file loaded by `include` or added explicitly by `include_dependency` is unchanged, or equal to the modification time truncated to the nearest second (to accommodate systems that can't copy mtime with sub-second accuracy). It also takes into account whether the path to the file chosen -by the search logic in `require` matches the path that had created the precompile file. It also takes -into account the set of dependencies already loaded into the current process and won't recompile those -modules, even if their files change or disappear, in order to avoid creating incompatibilities between +by the search logic in `require` matches the path that had created the precompile file. It also takes +into account the set of dependencies already loaded into the current process and won't recompile those +modules, even if their files change or disappear, in order to avoid creating incompatibilities between the running system and the precompile cache. If you know that a module is *not* safe to precompile your module