File: help_apoo.txt

package info (click to toggle)
apoo 2.2-2
  • links: PTS
  • area: main
  • in suites: jessie, jessie-kfreebsd, squeeze, wheezy
  • size: 560 kB
  • ctags: 425
  • sloc: python: 3,092; perl: 100; makefile: 56; sh: 4
file content (96 lines) | stat: -rw-r--r-- 2,760 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96

-------------------------------------------------------------------
		      Apoo Workbench 

   Copyright (C) 1998-2002 Rogério Reis & Nelma Moreira {rvr,nam}@ncc.up.pt


-------------------------------------------------------------------

The Apoo Workbench is an environment to monitoring the execution of a
Virtual Processor Unit.  During the execution of a program, it shows
the contents of the program counter, registers and memory data. The
program in memory is displayed in an Assembly language (not in a
machine language). As is usual with processor units emulators, Apoo
has two memory segments: the program-segment and the data-segment. In
this way, both addresses for program instructions and data will begin
in 0.

The Apoo Workbench allows also the editing/saving of the text program,
providing an easy way to write/edit/debug/execute Apoo assembly programs.


Execution:
---------

To execute a program in the Apoo Virtual Processor Unit you must first or:

   - enter in Edit Mode and write its instructions
   - open a text file with its code

After that, you can Load it; if a "parsing error" occurs, enter edit mode
and correct it; the interface will show the text line in which the error
occurred.

When the program is loaded (in memory) you can execute it in three ways:
     
     - Run: will execute all the instructions 
 
     - Step: will execute the next instruction and the values of the
       program counter, registers and memory data will be updated; the
       next instruction line, if exists, will have the background
       white
    
     - Cont: will execute instructions until the next breakpoint


In an instruction line, you can set/clear a breakpoint: 

- to set a breakpoint: Press <Double>-Button1 in that line (the
			  foreground will become green)

- to clear breakpoint: Press <Double>-Button2 (the foreground will
                	  become black)

The button labeled Clear can be used to clear all breakpoints 

Edit Mode:
---------

In edit mode you can change the text code of a program or create a new
one. To enter Edit Mode press the Edit button or New button.
After editing you can Save or SaveAs the current edited text.
You leave Edit Mode by loading the program (Load button) or opening a
new file.

The following emacs-like commands are implemented:

  <Control-k> 	kill-line 
  <Control-y> 	yank 
  <Control-w> 	kill-region 
  <Escape>w	copy-region-as-kill 
  <Control-at>	set-mark-command

  <Control-a>  beginning-of-line
  <Control-e>  end-of-line
  <Control-Home>  beginning-of-buffer 
  <Control-End>	end-of-buffer 
  <Control-d>	deletes the character to the right of the
                insertion cursor.







----------------------------- The End ---------------------------------