1 | -------------------------
|
---|
2 | | Release note May 2003 |
|
---|
3 | -------------------------
|
---|
4 | STOOD 4.3.8 (Windows) 20.05.2003
|
---|
5 | STOOD 4.3.9 (Unix) 20.05.2003
|
---|
6 | -----------------------------------
|
---|
7 |
|
---|
8 | ==========================================================
|
---|
9 | Changes since previous distribution:
|
---|
10 | ( v 4.3.2 (Windows) and v 4.3.3 (Unix), 19 February 2003 )
|
---|
11 | ==========================================================
|
---|
12 |
|
---|
13 |
|
---|
14 | 1. Changes
|
---|
15 | ----------
|
---|
16 |
|
---|
17 | 03.025 (06 Mar 03)
|
---|
18 | The C code generation rules produced a .c file for a terminal module,
|
---|
19 | even if it didn't provide any operation and didn't contain any
|
---|
20 | internal entity.
|
---|
21 | => Fixed in config/code_extractors/c [C091]
|
---|
22 |
|
---|
23 | 03.026 (13 Mar 03)
|
---|
24 | It was not possible to convert a generic into a design. The only way to
|
---|
25 | change the type of a design, was to patch the Stood.sto file manually. An
|
---|
26 | hidden function in the debug menu is now provided for that.
|
---|
27 | => Fixed in the kernel
|
---|
28 |
|
---|
29 | 03.027 (13 Mar 03)
|
---|
30 | Bad management of the dot notation for implemented_by operations. When
|
---|
31 | dot notations were used in operation signatures for parameter types, the
|
---|
32 | creation of an implemented_by link removed these dot notations. The
|
---|
33 | consequence was that the generated code couldn't compile any more.
|
---|
34 | => Fixed in the kernel
|
---|
35 |
|
---|
36 | 03.028 (14 Mar 03)
|
---|
37 | Missing procedures for sets. For the DataBase description file, there
|
---|
38 | was procedures to specify the contents for all the kinds of sets (op:
|
---|
39 | 81, ty: 82, co: 83, ex: 84 and da: 85), but procedures to specify the
|
---|
40 | set name (52), the set definition (37) and the set implemented_by (66)
|
---|
41 | were only available for operations. The procs 81, 52, 37 and 66 can now be
|
---|
42 | used for all kind of sets.
|
---|
43 | => Fixed in the kernel
|
---|
44 |
|
---|
45 | 03.029 (14 Mar 03)
|
---|
46 | Change of target_language was not saved. If the default target language was
|
---|
47 | changed in the option dialog box, and the design was saved before any
|
---|
48 | other change in the design, then the change tag was not set and the
|
---|
49 | default language modification was lost.
|
---|
50 | => Fixed in the kernel
|
---|
51 |
|
---|
52 | 03.031 (18 Mar 03)
|
---|
53 | It was not possible to save the changes made to the printing order of the
|
---|
54 | modules. It was possible to modify the order of the modules before
|
---|
55 | generating the design documentation. However these changes were not
|
---|
56 | saved.
|
---|
57 | => Fixed in the kernel
|
---|
58 |
|
---|
59 | 03.032 (18 Mar 03)
|
---|
60 | It was not possible to reload an initialization file. It could be
|
---|
61 | sometimes necessary to reload the initialization file. This feature is
|
---|
62 | now available from the "debug" menu.
|
---|
63 | => Fixed in the kernel
|
---|
64 |
|
---|
65 | 03.033 (20 Feb 03)
|
---|
66 | No warning when closing a design with a pending text edition. The last
|
---|
67 | pending text edition was lost when closing the design. A warning is now raised.
|
---|
68 | => Fixed in the kernel
|
---|
69 |
|
---|
70 | 03.035 (27 Feb 03)
|
---|
71 | There's now a new category in the "database" checker. It produces a file
|
---|
72 | describing the hierarchy of the modules.
|
---|
73 | => Fixed in config/checkers/database
|
---|
74 |
|
---|
75 | 03.036 (24 Mar 03)
|
---|
76 | The [R] flag was always attached to the symbols even when it couldn't be
|
---|
77 | deduced from the source code analysis. It was possible to change that manually
|
---|
78 | but the change was overloaded at next change in the code. Now, the flag [?] is
|
---|
79 | used when the read/write status is unknown.
|
---|
80 | => Fixed in the kernel
|
---|
81 |
|
---|
82 | 03.037 (24 Mar 03)
|
---|
83 | There was a context clause missing when generating an Op_Control as a separate
|
---|
84 | subunit.
|
---|
85 | => Fixed in config/code_extractors/ada [ADA177]
|
---|
86 |
|
---|
87 | 03.038 (01 Apr 03)
|
---|
88 | Crash when saving code extraction window while a checker was open. An
|
---|
89 | exception "message not understood 10533" was raised when the "save" menu
|
---|
90 | of a code extractor window was activated while a checker window was open.
|
---|
91 | => Fixed in the kernel
|
---|
92 |
|
---|
93 | 03.040 (02 Apr 03)
|
---|
94 | Need a filtering function to only show terminal entities in x-ref table.
|
---|
95 | New menu items have been added to the x-ref editor to apply a filter, in
|
---|
96 | order to hide the implemented_by links "Compact Implemented_by Links",
|
---|
97 | and to reset all the current filters "Reset all filters". For
|
---|
98 | documentation, two new Database procedures 96 and 97 have been created
|
---|
99 | to provide the same output as the respective existing proc 91 (uses) and
|
---|
100 | 93 (is used by), but without the implemented_by information.
|
---|
101 | => Fixed in the kernel
|
---|
102 |
|
---|
103 | 03.041 (07 Apr 03)
|
---|
104 | Ada reverse engineering: couldn't recognize exceptions in the root package
|
---|
105 | => Fixed in config/reverse/ada [REV036]
|
---|
106 |
|
---|
107 | 03.042 (08 Apr 03)
|
---|
108 | Ada code generation: problem occured with pragma "nesting"
|
---|
109 | => Fixed in config/code_extractors/ada [ADA178-ADA179]
|
---|
110 |
|
---|
111 | 03.043 (03 Apr 03)
|
---|
112 | It was possible to create two transitions with the same label in a
|
---|
113 | State-Transition Diagram.
|
---|
114 | => Fixed in the kernel
|
---|
115 |
|
---|
116 | 03.045 (08 Apr 03)
|
---|
117 | Need a solution to avoid code generation for some modules. This could be
|
---|
118 | used for instance for modules which code has already been generated by
|
---|
119 | another tool, like SCADE (or Sildex ?). The pragma "except" can now be used for that.
|
---|
120 | The name of the pragma can be customized with the property "NoCleanUpFor" in the
|
---|
121 | initialization file.
|
---|
122 | => Fixed in the kernel, and in the code generators.
|
---|
123 |
|
---|
124 | 03.046 (08 Apr 03)
|
---|
125 | Change notification should be performed at import time, not at export
|
---|
126 | time. This is due to the fact that when a module is exported, its status changes.
|
---|
127 | A new property "MarkExportedModules" have been added to the initialization
|
---|
128 | file to avoid changes at export time, if needed.
|
---|
129 | => Fixed in the kernel.
|
---|
130 |
|
---|
131 | 03.048 (09 Apr 03)
|
---|
132 | Need to recognize "var->field" syntax while scanning pseudo code
|
---|
133 | => Fixed in scan_pseudo
|
---|
134 |
|
---|
135 | 03.050 (11 Apr 03)
|
---|
136 | Need to change a Constant into a Data and reverse. A menu "convert to
|
---|
137 | constant/data" has been added in the graphic editor. Files will
|
---|
138 | follow the change if their logical names match (i.e. CstTxt <-> DataTxt)
|
---|
139 | => Fixed in the kernel
|
---|
140 |
|
---|
141 | 03.053 (22 Apr 03)
|
---|
142 | There was a syntax error when importing a CASEML file.
|
---|
143 | => Fixed in the kernel
|
---|
144 |
|
---|
145 | 03.056 (23 Apr 03)
|
---|
146 | Missing predicates "isRead" & "isWritten" for parameters in pseudo code. This
|
---|
147 | is useful to check the consistency of the pseudo code with the
|
---|
148 | passing mode of the parameters in the operation declaration.
|
---|
149 | => Fixed in the kernel
|
---|
150 |
|
---|
151 | 03.057 (06 May 03)
|
---|
152 | The sbprolog engine was linked with the libc v5 on Linux. It is now linked with
|
---|
153 | libc v6.
|
---|
154 | => Fixed in bin.pclinux/sbprolog
|
---|
155 |
|
---|
156 | 03.058 (30 Apr 03)
|
---|
157 | The subprogram parameter list wasn't properly generated in AADL
|
---|
158 | => Fixed in the AADL code generator [AADL002]
|
---|
159 |
|
---|
160 | 03.059 (13 May 03)
|
---|
161 | Use of special characters in identifier names generated errors when importing a
|
---|
162 | SIF file generated by OpenTool/UML. This is due to the restricted syntax of the
|
---|
163 | SIF format.
|
---|
164 | => Fixed in the OpenTool configuration file "hood.br"
|
---|
165 |
|
---|
166 | 03.060 (15 May 03)
|
---|
167 | When an Instance_Of module was created, the corresponding files were copied into
|
---|
168 | from the corresponding Generic directory to the destination Design directory with
|
---|
169 | the same user rights as in the Generic. If the Generic is write protected, then
|
---|
170 | the Instance_Of became also write protected. This can be customized by editing
|
---|
171 | the "copydir.sh" shell script.
|
---|
172 | => Fixed in config/internalTools/copydir.sh
|
---|
173 |
|
---|
174 | 03.063 (16 May 03)
|
---|
175 | When generating Ada source files, if the operation definition is empty in the design
|
---|
176 | database, then a "begin; null;" contents was automatically inserted by the Ada code
|
---|
177 | generator, in order not to prevent compilation. However, this code wasn't appropriate
|
---|
178 | for functions.
|
---|
179 | => Fixed in config/code_extractors/ada [ADA181]
|
---|
180 |
|
---|
181 | 03.064 (16 May 03)
|
---|
182 | It wasn't possible to declare an instance of an Ada generic subprogram in a non terminal
|
---|
183 | module. This was due to a lack of the parameter list. Now, the full parameter list may
|
---|
184 | be specified at any level, but a pragma "instance_op" must be used at code generation
|
---|
185 | phase. For SIF compatibility, the pragma "generic" has also be renamed into "generic_op"
|
---|
186 | and must be used to generate the code for the generic declaration of a subprogram.
|
---|
187 | => Fixed in config/code_extractors/ada [ADA180]
|
---|
188 |
|
---|
189 | 03.065 (19 May 03)
|
---|
190 | When an Environment is declared within the local System_Configuration of a Design, the
|
---|
191 | corresponding pragmas were not copied. A new shell script "copyenv.sh" may now be used
|
---|
192 | to customize what needs to be copied when updating the Environment declarations. The current
|
---|
193 | default behaviour is that the pragma file is copied if it doesn't already exist.
|
---|
194 | => Fixed in config/internalTools/copyenv.sh
|
---|
195 |
|
---|
196 | 03.066 (20 May 03)
|
---|
197 | The Ada source filenames generated by Stood were not always fully compliant with the GNAT
|
---|
198 | file naming rules. To avoid these problems, a file gnat.adc is now produced to map Ada units
|
---|
199 | and source filenames.
|
---|
200 | => Fixed in config/code_extractors/ada [ADA182]
|
---|
201 |
|
---|
202 | 03.067 (20 May 03)
|
---|
203 | Some Ada context clauses were missing when the body of operations were included inside
|
---|
204 | the body of the relevant package.
|
---|
205 | => Fixed in config/code_extractors/ada [ADA183]
|
---|
206 |
|
---|
207 | 03.068 (21 May 03)
|
---|
208 | The Ada code generated for instances of generic packages was not always correct. A new pragma
|
---|
209 | "with" has been introduced to specify the name of the generic unit that must be withed from
|
---|
210 | the instanciated package. This pragma must be defined in the generic, and will be copied into
|
---|
211 | all the instances.
|
---|
212 | => Fixed in config/code_extractors/ada [ADA184]
|
---|
213 |
|
---|
214 | 03.069 (23 May 03)
|
---|
215 | In some cases, the SIF file produced by the Ada reverse engineering engine was syntactically
|
---|
216 | incorrect. A END statemend was missing for the root module.
|
---|
217 | => Fixed in config/reverse/ada [REV037]
|
---|
218 |
|
---|
219 | 03.070 (26 May 03)
|
---|
220 | Various improvements have been made in the Ada and C reverse engineering rules:
|
---|
221 | - no more root_body hierarchy when the root module is unique (Ada and C) [REV038][REVC005]
|
---|
222 | - removing module name prefix that could have been introduced by the C code generator [REVC006]
|
---|
223 | - removing all the void parameters (C) [REVC007]
|
---|
224 |
|
---|
225 |
|
---|
226 | 2. Changed files
|
---|
227 | ----------------
|
---|
228 |
|
---|
229 | 2.1. Binary files
|
---|
230 |
|
---|
231 | bin.w32/stood.ini
|
---|
232 | bin.w32/stood.exe
|
---|
233 | bin.w32/stood.eng
|
---|
234 | bin.w32/scan_pseudo.exe
|
---|
235 |
|
---|
236 | bin.sol2/stood
|
---|
237 | bin.sol2/stood.eng
|
---|
238 | bin.sol2/scan_pseudo
|
---|
239 | bin.sol2/.stoodrc
|
---|
240 |
|
---|
241 | bin.aix4/stood
|
---|
242 | bin.aix4/stood.eng
|
---|
243 | bin.aix4/scan_pseudo
|
---|
244 | bin.aix4/.stoodrc
|
---|
245 |
|
---|
246 | bin.hpux9/stood
|
---|
247 | bin.hpux9/stood.eng
|
---|
248 | bin.hpux9/scan_pseudo
|
---|
249 | bin.hpux9/.stoodrc
|
---|
250 |
|
---|
251 | bin.pclinux/stood
|
---|
252 | bin.pclinux/stood.eng
|
---|
253 | bin.pclinux/scan_pseudo
|
---|
254 | bin.pclinux/.stoodrc
|
---|
255 | bin.pclinux/sbprolog
|
---|
256 |
|
---|
257 | 2.2. Configuration files
|
---|
258 |
|
---|
259 | config/code_extractors/ada/Extract.pro
|
---|
260 | config/code_extractors/ada/Extract.sbp
|
---|
261 | config/code_extractors/ada/Input.sbp
|
---|
262 | config/code_extractors/ada/pragma
|
---|
263 |
|
---|
264 | config/code_extractors/c/Extract.pro
|
---|
265 | config/code_extractors/c/Extract.sbp
|
---|
266 | config/code_extractors/c/Input.sbp
|
---|
267 | config/code_extractors/c/pragma
|
---|
268 |
|
---|
269 | config/code_extractors/aadl/Extract.pro
|
---|
270 | config/code_extractors/aadl/Extract.sbp
|
---|
271 | config/code_extractors/aadl/Input.sbp
|
---|
272 |
|
---|
273 | config/reverse/ada/Extract.pro
|
---|
274 | config/reverse/ada/Extract.sbp
|
---|
275 | config/reverse/ada/Input.sbp
|
---|
276 |
|
---|
277 | config/reverse/c/Extract.pro
|
---|
278 | config/reverse/c/Extract.sbp
|
---|
279 | config/reverse/c/Input.sbp
|
---|
280 |
|
---|
281 | config/internalTools/copydir.sh
|
---|
282 | config/internalTools/copyenv.sh
|
---|
283 |
|
---|
284 | 2.3. Others
|
---|
285 |
|
---|
286 | examples, libs and tutorial directories have been updated |
---|