Author:halw

Date:2009-01-06T21:31:01.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@153 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-01-06 21:31:01 +00:00
parent 2fa0e9a0ae
commit 8805352e2a
16 changed files with 117 additions and 129 deletions

View File

@@ -27,29 +27,29 @@ It is also possible to dynamically start and stop the profiler in a program. To
In the root feature:
<code>
local
ps: PROFILING_SETTING
-- Other local variables if necessary.
do
create ps.make
ps.stop_profiling
-- Real program execution.
ps.start_profiling
end</code>
local
ps: PROFILING_SETTING
-- Other local variables if necessary.
do
create ps.make
ps.stop_profiling
-- Real program execution.
ps.start_profiling
end</code>
And in the feature(s) that needs to be profiled:
<code></code>
<code>
local
ps: PROFILING_SETTING
-- Other local variables if necessary.
do
create ps.make
ps.start_profiling
-- What needs to be profiled.
ps.stop_profiling
end</code>
local
ps: PROFILING_SETTING
-- Other local variables if necessary.
do
create ps.make
ps.start_profiling
-- What needs to be profiled.
ps.stop_profiling
end</code>
{{note|Even if the profiler should only work in certain sections of code, the '''Profiling''' check box of the [[General Target Options|Projects Settings]] dialog must be checked or the '''profile''' option must be set on certain clusters. }}