You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/usage/Compile.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,9 @@ Users can compile and catalog BASIC programs using this extension.
5
5
**Note**:
6
6
7
7
- Before compiling BASIC programs, a U2 server must be connected. For information on connecting to a U2 server, please see [this section](./Connection.md).
8
-
- After compiling, regardless of whether the compile succeeds or fails, the BASIC files will be synchronized to the U2 server, overwriting the existing ones and new files will also be created.
8
+
- After compiling, regardless of whether the compile succeeds or fails, the BASIC files will be synchronized to the U2 server, overwriting the existing ones and new files will also be created.
9
9
- Generated objective files will not be synchronized from the server to the local machine.
10
-
- Compilation does not work properly when VS Code and the extension run on Linux platform.
10
+
- Compilation does not work properly when VS Code and the extension installed on Linux platform.
11
11
12
12
## Compile and catalog
13
13
@@ -45,7 +45,7 @@ By using VS Code task, users can compile or catalog multiple BASIC programs at t
45
45
46
46
#### Create a BASIC build task
47
47
48
-
Select "Run Build Task ..." from the "Terminal" menu to open the Command Palette.
48
+
Select "Configure Default Build Task ..." or "Configure Tasks ..." from the "Terminal" menu to open the Command Palette.
Copy file name to clipboardExpand all lines: docs/usage/Debugging.md
+27-55Lines changed: 27 additions & 55 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,72 +1,34 @@
1
1
## Debugging (Preview)
2
2
3
-
With the debugging function, you can easily debug BASIC programs, observe, track the results and changes to variables for each step when running a BASIC program.
3
+
With the debugging function, user can easily debug BASIC programs, observe, track the results and changes to variables for each step when running a BASIC program.
4
4
5
-
The current version of the debugging function is a preview version and is only supported for UniVerse the v11.3.4 and 12.1.1 releases. There are limits to debugging features and not all debugging functions are stable.
5
+
The 1.7.0 version of the debugging function is a preview version. There are limitations to the debugging features and not all debugging functions are stable. The following U2 server versions and platforms are supported:
6
6
7
-
Please refer [Known issues](./KnownIssues.md) list to find out existing issues in debugging feature.
8
-
9
-
### Setup Environment
10
-
11
-
To support the debugging function, a DAP server will run on the UniVerse server side. In this preview version, you need download the DAP server binaries and add them to UniVerse manually. In future releases, this process will be automated.
12
-
13
-
### Downloading DAP Server
14
-
15
-
You must login to [RBC platform](https://rbc.rocketsoftware.com/) to download DAP server binaries. Follow below steps to download related binaries:
16
-
17
-
1) Click button "Search Product Availability"
18
-
19
-
2) Select "Product" to "MV BASIC for VS Code", and select "Windows" (binaries for Linux platform are also in this package)
20
-
21
-
3) In "1.6.0" release, click the "Product" download link
22
-
23
-
### Installing the DAP server binaries
24
-
25
-
You need copy the DAP binaries to the U2 server manually. Complete the steps below to configure the environment.
26
-
27
-
#### Linux Platform
28
-
29
-
1) Copy **uvdap_server** and **uvdap_slave** to the *$UVHOME/bin* folder. *$UVHOME* is the installation path for UniVerse.
30
-
31
-
Ensure permission accordingly to installed release for permission, owner, and group similar to **uvapi_server** and **uvapi_slave**.
32
-
33
-
2) Open the **unishared** folder and find the unirpc services file (unishared/unirpc/unirpcservices). Ensure you have write permissions to the file.
34
-
35
-
3) Open the **unirpcservices** file and add the following new line to unirpcservices:
36
-
37
-
```
38
-
uvdaps <absolute file path of uvdap_server> * TCP/IP 0 3600
39
-
```
7
+
### UniVerse
40
8
41
-
**Note**: You will need to change to the root user to update this file.
9
+
Versions: 12.1.1 and before
42
10
43
-
If you encounter some permission issues during debugging, please try following commands to change these binaries' ownership.
11
+
Platforms: Windows, Linux, AIX
44
12
45
-
```
46
-
chmod 755 uvdap*
47
-
chown uvdb uvdap*
48
-
chgrp input uvdap*
49
-
```
13
+
### UniData
50
14
51
-
#### Windows Platform
15
+
Versions: 8.2.4
52
16
53
-
1) Copy the **uvdap_server.exe** and **uvdap_slave.exe** files to the UniVerse bin folder. By default, UniVerse is installed to **"C:\U2\UV"**, and its bin folder is **"C:\U2\UV\bin"**.
17
+
Platforms: Windows, Linux, AIX
54
18
55
-
2) Open the **unishared** folder and find the unirpc services file named **unirpcservices**. By default, the **unishared** folder installation path is **"C:\U2\unishared"**, and you can find file **unirpcservices** under **"C:\U2\unishared\unirpc"**.
19
+
Please refer [Known issues](./KnownIssues.md) list to find out existing issues in debugging feature.
56
20
57
-
3) Open file **unirpcservices** file and add the following new line to it:
21
+
### Setup Environment
58
22
59
-
```
60
-
uvdaps <absolute file path of uvdap_server> * TCP/IP 0 3600
61
-
```
23
+
In the 1.6.0 release, additional binaries should be installed on UniVerse to support the debugging features. This is no longer necessary for the 1.7.0 release.
62
24
63
25
## Start Debugging
64
26
65
-
### Connecting to a UniVerse account folder
27
+
### Connecting to a U2 server account folder
66
28
67
-
Before using the debugging feature, you must first connect to a UniVerse account folder. Please see the [Connection section](./Connection.md) to learn how to connect to a UniVerse server.
29
+
Before using the debugging feature, you must connect to a U2 server account folder firstly. Please see the [Connection section](./Connection.md) to learn how to connect to a U2 server account.
68
30
69
-
**Note**: The debugging feature only works on **UniVerse** 11.3.4 and 12.1.1 releases in this preview version. The debugging feature will not work if you only open a single BASIC program file in VS Code. You must open an account folder.
31
+
**Note**: The debugging feature will not work if you only open a single BASIC program file in VS Code. You must open an account folder.
70
32
71
33
### Debugging BASIC files
72
34
@@ -84,8 +46,6 @@ Before debugging, open the BASIC program first.
84
46
85
47
The BASIC program file will be compiled first. If successful, the debugging process will stop at the first runnable line of code in the program file.
86
48
87
-
88
-
89
49
### Debug with launch file
90
50
91
51
You can also configure a `launch.json` file for debugging.
@@ -153,21 +113,27 @@ The program will stop when the process encounters a break point.
153
113
154
114
When the process encounters a break point, the program will stop running. You can press the F5 key or click the Continue button from the debug panel to continue running the program.
155
115
116
+
**Note**: Program cannot jump out of a subroutine through this operation in UniVerse.
117
+
156
118
157
119
158
120
### Step over
159
121
160
122
The step over function allows you to run the program line-by-line. Press the F10 button or click the Step Over button from the debug panel to run one line of the program.
161
123
124
+
**Note**: Program cannot jump out of a subroutine through this operation in UniVerse.
125
+
162
126
163
127
164
128
### Step into and step out
165
129
166
130
These two operations are still not stable. They partially work if breakpoints are set at CALL line. Please refer [Known Issues](./KnownIssues.md).
167
131
132
+
**Note**: Program cannot jump out of a subroutine through **Step Out** operation in UniVerse.
133
+
168
134
## Restart debug
169
135
170
-
This operation is currently not supported.
136
+
This operation is currently NOT supported.
171
137
172
138
### Stop debugging
173
139
@@ -190,3 +156,9 @@ You can also add variables to the **WATCH** panel.
190
156
Click the plus (+) button from the **WATCH** panel and enter the variable name to display the variable’s value.
191
157
192
158
159
+
160
+
### Handle input operation
161
+
162
+
You can switch to the VS Code terminal to handle an INPUT statement during BASIC program running.
0 commit comments