Changes between Version 17 and Version 18 of ErlangShellInterface

Timestamp:

Jul 11, 2012, 3:12:23 PM (12 years ago)

Author:

manualwiki

Comment:

restruct. analysis, added if_layes

ErlangShellInterface

@@ -299 +299 @@
 There is a [[SemanticQuery|semantic queries]] page, where you can learn more about this topic.
 
-== Dependency analysis ==
-
-The two interface functions are:
+== Analysis ==
+=== Dependency analysis on function or module level ===
+There is a [[/wiki/Dependency/Functions|Module and Function Dependencies]] page, where you can learn more about this topic. 
+
+The command-line interface offers two interface functions, which are:
 
 1. For drawing:
@@ -312 +314 @@
 }}}
 
-=== Options ===
+==== Options ====
 
 The parameter of the interface functions is a proplist setting the options of the analysis. The available options are:
@@ -333 +335 @@
 You can specify entities either with graph nodes (such as {{{{'$gn', func, 123}}}}) or with their identifier. Modules can be specified with their names as atoms (e.g. 'mnesia'), while functions are specified by their MFA descriptor as a string (e.g. "io:format/2")
 
-=== Examples for listing results ===
+==== Examples for listing results ====
 
 * Checking for cycles in module level.
@@ -383 +385 @@
 ri:print_dep([{level, func}, {gnode, ["cycle4:f5/1"]}]).
 }}}
+
+=== Logical layers analysis ===
+In large program systems, groups of compilation units (in the case of Erlang, modules) usually form logical layers. A desired property of such systems is that code in one layer should only use the layer immediately below it, and conversely, provide functionality only for the layer immediately above it. If you would like to check whether a system observes this rule, you should visit the [[InterfaceLayers|Interface Layers]] page, which show you how to check it.
 
 == Server management command list ==