Author:admin

Date:2008-09-25T16:19:15.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@44 abb3cda0-5349-4a8f-a601-0c33ac3a8c38

documentation/current/eiffelstudio/eiffelstudio-how-tos/running-and-debugging/exploring-application-dynamic-state.wiki

@@ -9,7 +9,7 @@ To follow an object state between pauses of the application, pick and drop it in
 
 You can also query features dynamically by using the evaluation tool, which can be very useful to have glimpses of the C memory of the system, for instance.
 
-{{seealso| '''See Also''' <br/>
+{{seealso|<br/>
 [[Interrupting an application|Pausing an application]]  <br/>
 [[Callstack tool: Introduction|Call stack tool]]  <br/>
 [[Objects tool: Introduction|Object tool]]  <br/>

documentation/current/eiffelstudio/eiffelstudio-how-tos/running-and-debugging/handling-exceptions.wiki

@@ -7,7 +7,7 @@ The <eiffel>[[ref:/libraries/base/reference/exceptions_chart|EXCEPTIONS]] </eiff
 
 When an exception is raised while the application is being debugged, the application stops immediately and the debugger displays the context in which the exception occurred, whether or not the exception is rescued.
 
-{{seealso| '''See Also''': <br/>
+{{seealso|<br/>
 [[8 Design by Contract (tm), Assertions and Exceptions|Reference of exceptions]]  }}
 
 

documentation/current/eiffelstudio/eiffelstudio-how-tos/running-and-debugging/interrupting-application.wiki

@@ -9,7 +9,7 @@ Two methods can be used to pause a debugged application:
 
 To kill a debugged application, use the [[Stop a debugged application]] , located in both the debug menu and the project toolbar. 
 
-{{seealso| '''See Also''' <br/>
+{{seealso|<br/>
 [[Running an application|Running a program]]  <br/>
 [[Using breakpoints|Using breakpoints]]  }}
 

documentation/current/eiffelstudio/eiffelstudio-how-tos/running-and-debugging/profiling.wiki

@@ -22,7 +22,7 @@ It is also possible to dynamically start and stop the profiler in a program. To
 * Call [[ref:libraries/base/reference/profiling_setting_flatshort|start_profiling]]  on this object to start the profiler. 
 * Call [[ref:libraries/base/reference/profiling_setting_flatshort|stop_profiling]]  on this object to stop the profiler. 
 
-{{tip| '''Tip''': To profile only part of a program, turn off the profiler at the very beginning of the program, turn it on just before the part of the code that should be profiled, and turn it back off after this section. Typically, it results in the following code: }}
+{{tip|To profile only part of a program, turn off the profiler at the very beginning of the program, turn it on just before the part of the code that should be profiled, and turn it back off after this section. Typically, it results in the following code: }}
 
 In the root feature:
 
@@ -52,17 +52,17 @@ And in the feature(s) that needs to be profiled:
 	end</code>
 
 
-{{note| '''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. }}
+{{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. }}
 
 Once the profiler has been enabled and the program has been recompiled, it is necessary to launch the program.
 
-{{tip| '''Tip''': It is possible to profile debuggable(frozen/melted) executables as well as finalized ones. It is more interesting to profile finalized executables, though, since the execution speed is more representative of what will be obtained by your end users. }}
+{{tip|It is possible to profile debuggable(frozen/melted) executables as well as finalized ones. It is more interesting to profile finalized executables, though, since the execution speed is more representative of what will be obtained by your end users. }}
 
 When the program exits, a file named 'profinfo' should be generated next to it.
 
 All that's left to do is launch the [[Profiler wizard: Introduction|Profiler wizard]]  and follow the instructions. 
 
-{{seealso| '''See Also''' <br/>
+{{seealso|<br/>
 [[Generating executables|Generating executables]]  <br/>
 [[Running an application|Running a program]]  <br/>
 [[Tuning a program|Tuning a program]]  }}

documentation/current/eiffelstudio/eiffelstudio-how-tos/running-and-debugging/running-application.wiki

@@ -12,13 +12,13 @@ Melted and frozen executables can be debugged. Several methods can be used to la
 ** The [[Step out of a feature]] , which launches the application and stops it as soon as the application exits the feature it is stopped in. 
 
 
-{{tip| '''Tip''': All the above commands can be accessed either in the '''Project''' toolbar or in the '''Debug''' menu. <br/>
+{{tip|All the above commands can be accessed either in the '''Project''' toolbar or in the '''Debug''' menu. <br/>
 They can be used either to launch the program or to resume its execution after it has been paused. }}
 * It is also possible to select '''Run to breakpoint''' in a [[Breakpoint editing|breakpoint context menu]]  to have the application be launched and executed until it reaches the selected execution line. 
 
 Finalized executables can also be run, but they are not debuggable and cannot be interrupted. To run a finalized executable, use the [[Run a finalized executable]] , located in the '''Project''' menu and the '''Project''' toolbar. 
 
-{{seealso| '''See Also''' <br/>
+{{seealso|<br/>
 [[Generating executables|Compiling an executable]]  <br/>
 [[Using breakpoints|Using breakpoints]]  <br/>
 [[Interrupting an application|Interrupting an application]]  }}

documentation/current/eiffelstudio/eiffelstudio-how-tos/running-and-debugging/setting-command-line-arguments.wiki

@@ -8,7 +8,7 @@ To change the command line arguments used when debugging:
 * In this dialog, you can change the current arguments and also store and load argument sets. 
 * Click '''OK'''. 
 
-{{tip| '''Tip''': To get the command line arguments in a program, it is possible to either define the root feature as taking an array of [[ref:/libraries/base/reference/string_8_chart|STRING_8]]  objects, or to use the [[ref:/libraries/base/reference/arguments_chart|ARGUMENTS]]  class, which provides a lot of functionality linked with command line arguments. }}
+{{tip|To get the command line arguments in a program, it is possible to either define the root feature as taking an array of [[ref:/libraries/base/reference/string_8_chart|STRING_8]]  objects, or to use the [[ref:/libraries/base/reference/arguments_chart|ARGUMENTS]]  class, which provides a lot of functionality linked with command line arguments. }}
 
 
 

documentation/current/eiffelstudio/eiffelstudio-how-tos/running-and-debugging/using-breakpoints.wiki

@@ -5,7 +5,7 @@ To change the status of one breakpoint, it is possible to use the [[Breakpoint e
 
 To change the status of several breakpoints at the same time, the easiest way is to use the [[Breakpoint commands|breakpoints-related commands]] , which have actions at feature-scope, class-scope and system-scope. 
 
-{{seealso| '''See Also''' <br/>
+{{seealso|<br/>
 [[Running an application|Running an application]]  <br/>
 [[Interrupting an application|Interrupting an application]]  <br/>
 [[Breakpoints: Introduction|Breakpoints reference]]  }}

documentation/current/eiffelstudio/eiffelstudio-how-tos/running-and-debugging/using-debug-clauses.wiki

@@ -22,7 +22,7 @@ To modify the debug clauses status:
 * Click '''OK'''. 
 * You must [[Generating executables|recompile]]  your project for the changes to take effect. 
 
-{{tip| '''Tip''': Debug clauses make it easy to remove all debug messages when finalizing a system. }}
+{{tip|Debug clauses make it easy to remove all debug messages when finalizing a system. }}