From cb119ebc0e923b6b85a8352ef71012eb431b54d5 Mon Sep 17 00:00:00 2001
From: Lukas Larsson
Date: Wed, 2 Feb 2011 10:52:42 +0100
Subject: Update documentation to reflect performance enhancement changes of
cover
---
lib/tools/doc/src/cover.xml | 29 +++++++++++++++++++++++++++++
lib/tools/doc/src/cover_chapter.xml | 7 +++++++
2 files changed, 36 insertions(+)
(limited to 'lib/tools/doc/src')
diff --git a/lib/tools/doc/src/cover.xml b/lib/tools/doc/src/cover.xml
index 323bd0dda8..0a3302bda5 100644
--- a/lib/tools/doc/src/cover.xml
+++ b/lib/tools/doc/src/cover.xml
@@ -270,6 +270,8 @@
defaults to function.
If Module is not Cover compiled, the function returns
{error,{not_cover_compiled,Module}}.
+ HINT: It is possible to issue multiple analyse_to_file commands at
+ the same time.
@@ -307,6 +309,33 @@
.beam file, or in ../src relative to that
directory. If no source code is found,
,{error,no_source_code_found} is returned.
+ HINT: It is possible to issue multiple analyse_to_file commands at
+ the same time.
+
+
+
+ async_analyse_to_file(Module) ->
+ async_analyse_to_file(Module,Options) ->
+ async_analyse_to_file(Module, OutFile) ->
+ async_analyse_to_file(Module, OutFile, Options) -> pid()
+ Asynchronous call to analyse_to_file.
+
+ Module = atom()
+ OutFile = string()
+ Options = [Option]
+ Option = html
+ Error = {not_cover_compiled,Module} | {file,File,Reason} | no_source_code_found | not_main_node
+ File = string()
+ Reason = term()
+
+
+ This function works exactly the same way as
+ analyse_to_file except
+ that it is asynchronous instead of synchronous. The spawned process
+ will link with the caller when created. If an Error occurs
+ while doing the cover analysis the process will crash with the same
+ error reason as analyse_to_file
+ would return.
diff --git a/lib/tools/doc/src/cover_chapter.xml b/lib/tools/doc/src/cover_chapter.xml
index b4f7919183..92a790c34e 100644
--- a/lib/tools/doc/src/cover_chapter.xml
+++ b/lib/tools/doc/src/cover_chapter.xml
@@ -403,6 +403,13 @@ ok
database contains information about each executable line in each
Cover compiled module, performance decreases proportionally to
the size and number of the Cover compiled modules.
+ To improve performance when analysing cover results it is possible
+ to do multiple calls to analyse
+ and analyse_to_file
+ at once. You can also use the
+ async_analyse_to_file
+ convenience function.
+