(Build b943) – 25 May 2018
- Added ‘call ptr’ reference between Qt signals and slots referenced in connect calls.
(Build b942) – 22 May 2018
- Full support for C# 7.0, 7.1 and 7.2 has been added
- Fixed lookup of entities by ‘renameby’ reference.
- For Java, fixed bug where overloaded functions merged if all parameters have types with the same short names.
- Fixed failure to search for include files among project files when the file encoding is different from the system locale encoding.
(Build b941) – 11 May 2018
- For C#, added support for some C# 7 pattern matching.
- Updated Find in Files to save the configuration changes on a more dynamic basis. Also added the ability to only search the currently selected open file.
- Fixed a Find in Files issue where §§§ search string was not being properly identified in relative project files.
Function pointer support is available in Understand 5.0 when using the C/C++ Strict Parser. With this added support, Understand is providing the potential calls so that you can see the bigger picture.
This screenshot shows the Information Browser in Understand 4.0 on the left, and Understand 5.0 on the right, with the same project and the same function being viewed in each version. Understand 4.0 shows only a few calls, while Understand 5.0 is providing all of the possibilities with the added function pointer support.
This also translates to a better, more informative graphical view with the added function pointers. You can see in this next graph, all of the red dots on the nodes which signify the ability to expand the calls.
Notice that the same ‘dthash’ function, prior to function pointer support, only had 2 nodes that were expandable.
Looking at a few of the entities in this call graph, we expand the ‘cmpf’, ‘makef’, and ‘dthtab’ calls and see the potential calls available, noting that the function pointer calls are signified with the red dotted lines.
Here is the same graph available in Understand 4.0 prior to the function pointer support.
Understand 5.0 is now available! Here is what has changed since Understand 4.0 was released:
- Visual Basic Support
- Codecheck Comment Keywords
- Application wide color schemes
- License Tracking
- Previewer window
- Annotation of individual lines
- VHDL control flow graph
- Java & C# UML Sequence diagrams
- Support for FORTRAN 2008
- Hersteller Initiative Software Codechecks
- Additional Codechecks
- C++14 Support in Strict parser
- Mac build bundled into .app to be compatible with MacOS Sierra
- MSVC 2015 Support
- Support for JIPSE MIL-STD-1750A assembly language
- C# Version 6 Support
- Assembly IBM System 370 including Control Flow Graph
- Visual Studio 2017 C++
- Pascal86 Syntax
Understand 5.0 is also being released along with Helios™, our new licensing system, to give you better user mobility, easier licensing management, and more control.
The interactive Cluster Call Graphs show the function call graph, organized by file. There are several variants of this graph: Call, Call-by, Butterfly and Internal Call. They can also be accessed from the function, class, file or architecture level. These graphs can all be accessed from the Graphical View right click menu for the entity.
Cluster Call Butterfly Graph
Cluster Callby Graph
Cluster Call Graph
Cluster Call Internal Graph
Read more »
Good news for teams using Codecheck, build 868 lets Codecheck ignore violation via comments in the code. This will allow teams to specify areas in the code where exceptions are permitted and specify the rationale. For example:
goto RAINBOW; //UndCC_Line() Use of goto statement approved by Gerry T. on Nov 7,2014
This will create a new rule in the Codecheck “Ignores List” to ignore all Codecheck violations on this line and add a note about the approval process. Those ignored violations can still be viewed in Understand, but are hidden by default.
Ignore rules can be created for: a specific line, a range of lines, a file, a specific entity, and a specific entity in a range of lines. They can also be made to ignore all violations or just violations of the specified type(s).
In an effort to make our APIs more consistent a few of the API files have been moved around with build 858. Your code may need to be updated to reflect these changes.
udb.h, libudb_api.so, udb_api.dll and udb_api.lib have all been moved to bin\<OS>\C
The bin\pc-win64\python folder has been capitalized to bin\<OS>\Python
Custom Perl API
The Understand Perl library files have been moved up a level from bin\<OS>\Perl\STI\Maintain to bin\<OS>\Perl\STI
This will only affect users that are using the perl API with their own custom install of Perl 5.10.0, not those running scripts inside of Understand or using the uperl executable.
We’re excited to join our European partner Emenda at a morning seminar in Reading on Tuesday 18th October. The subject is:
Software quality improvement, development process optimisation and cost reduction
More details below, we hope to see you there!
Our European distributor, Emenda will be hosting two code quality seminars in France next month, we would love to see you there.
The first will be in Toulouse on October 11, and the second in Paris on October 13
More details below, à bientôt
Journée Technologique – Optimisation des coûts liés à la certification grâce aux outils
Darth Vader is a trademark of Disney, not SciTools.
Read more »
Do you ever wonder how many licenses are really being used? Are engineers saying they don’t have any licenses available when they need them? We have added Floating License Tracking to make answering these questions a little easier. After upgrading the License Manager to build 793 or later, the server administrator can choose a location to save the log file, and start logging right from the License Manager GUI.
Once the logging is enabled take a look at the different graphs that are available by selecting the ‘Reporting’ tab. If your license file consists of different major versions of Understand, they will be color coded and divided up accordingly.
License Usage by Month
License Usage by Week
License Usage Daily
Notice that these graphs also show the number of times that a license was denied, meaning that all of the licenses were already in use when an engineer tried to get a license. This can help a team know if they need more licenses and help determine how many are needed.
If you like to see the raw data, or just want to see some more details, take a look at the log table that is available under the Reporting->Log Table tab. If you still want more data than this, let us know and we can give you details about how to get even more with a little custom work.