Thema: Entwicklertools diverses

[SiLæncer]

Software Ideas Modeler is used to draw UML diagrams which are used in professional software development. Software Ideas Modeler can also be used to draw some other diagrams such as entity-relationship diagrams and UI mockups.

Main features:

    Intuitive and quick drawing of diagrams
    All UML 2.4 diagrams
    Flowcharts, Data Flow Diagrams, Entity Relationship Diagram (Crow Foot/Chen), CRC Cards, User Interface, Hierarchical Task Analysis, Entity Life History, Robustness Diagram, Concurrency Diagram, Venn Diagram, Mind Map, JSD diagrams
    Styling
    Print - batch printing, multiple pages per diagram
    Export diagrams to various image formats (BMP, PNG, JPG, GIF, TIFF, SVG, WMF, EMF) and PDF


Officially supports GNU/Linux via Mono.

Note: paid versions with additional features are also available.

License:    Free for non-commercial use

Changelog

Added option to show full project path [RQ#1533]
Added option to format virtual operation as italic [RQ#1532]
Added icons to ribbon/menu/toolbar configuration tree (Options dialog)
Fixed focus lost when using left/right arrows in combo box during diagram editing
Fixed parsing messages of UML sequence action
Fixed application crash when setting an existing operation to sequence message in sequence diagram
Fixed application crash after uploading project first time
Fixed displaying deleted solutions in server repository browser
Fixed displaying text alignment setting for setting group with different sub-settings [RQ#1529]
[Mono] Fixed application crash on start

[close]

http://www.softwareideas.net/

[SiLæncer]

Changelog

[Nov 20 2017]
FIXED: Possibly crash in AGC when another thread is doing findall. Keri Harris.
ENHANCED: library(prolog_colour): handling of cross-module calls.
FIXED: Avoid instantiation errors when colouring insufficiently instantiated goals.
ENHANCED: Colour library: classify m:Var and m:noncallable as errors.
FIXED: predicate_property(m:P, autoload(File)) raised an instantiation error instead of enumerating the autoloadable predicates.
PORT: Global generation handling on machines without atomic 64-bit operations. James Cowgill. This is a temporary workaround. On the long run we should use libatomic to guarantee properly ordered operations that are fully portable. This should be a temporary fix for 32-bit platforms (mips, mipsel, powerpc, powerpcspe)
[Nov 7 2017]
ADDED: Multiline CSV rows where newlines are embedded in quoted fields.
[Nov 11 2017]
FIXED: atom_is_named_var(): incorrect classification of wide-character atoms leading to false multiton messages. Arthur Wang.
FIXED: _<non-upper> is not subject to multiton check
[Nov 8 2017]
FIXED: atom-garbage collection when compiled for single threading. Abramo Bagnara.
[Nov 6 2017]
DOC: Document engine_destroy/1
[Nov 3 2017]
FIXED: maplist/N expansion for qualified goals. Samer Abdallah.
FIXED: Engine symbol's are not referenced to allow reclaiming engines in atom-gc. Thus, we should also not unregister them on completion.
DEBUG: Fix printing -1 reference issues
CLEANUP: Duplicate test in atom-completion
[Nov 2 2017]
CLEANUP: PL_unregister_atom(): style and properly check for references dropping below zero.
FIXED: veto atom-destruction in the type->release and GD->atoms.gc_hook.
[Nov 1 2017]
DOC: asserta/1,2, assertz/1,2, assert/1,2: join, add example.
Package jpl
[Nov 15 2017]
PORT: Find Java9 shared object dir from the java home.
[Nov 13 2017]
PORT: Also check new Java 9 directory structure
Package pldoc
[Nov 13 2017]
ENHANCED: Do not not include the synopsis when including a predicate documentation into markdown using [[Name/Arity]].
Package plunit
[Nov 22 2017]
ADDED: show_coverage/2. Predicate show_coverage/2 receives a list of module names of interest as second argument and it prints detailed information of the uncovered clauses that belong to any of those modules. Statistics have been improved. Clauses originated from system calls such as :-use_module or pldoc comments are no longer taken into account to compute for the total number of clauses in a file.
Package semweb
[Nov 22 2017]
FIXED: prioritize base URI explicitly set through option.
FIXED: File input clause for read_rdfa/3 would not be reached.
[Nov 4 2017]
PORT: ntriple parser for platform with unsigned char (arm)
[Nov 3 2017]
CLEANUP: Move RDF prefix handling into its own library as this can also be used for XML and other RDF backends.
FIXED: rdf_nth1/3, rdf_nth0/3: really raise a type error.
Package ssl
[Nov 13 2017]
ENHANCED: SAML certificate checking: ignore data appearing before the first BEGIN CERTIFICATE delineator and everything after the first END CERTIFICATE
Package xpce
[Nov 20 2017]
ADDED: PceEmacs: Support two context arguments for colour fragments

[close]

http://www.swi-prolog.org/

[SiLæncer]

Ron's HTML Cleaner permits you quickly to clean, or alter, a source HTML document or page via the use of user-defined cleaners.

The cleaners that you can use are created from a list of operations that can be built, saved and applied to any HTML document as required. Being able to clean an HTML document to remove redundant code and formatting issues can be useful if you intend on publishing a Blog or CMS for instance - Having all the formatting and code correctly done before going live can save some embarrassment from an improperly rendered page. It will allow you to create multiple rules that are taken into account during document processing. To process a document you simply specify the source and choose the desired cleaner. Ron's HTML Cleaner will automatically handle your content. For those that like a little more control, you do have the option to disengage the automatic processing.

License: Freeware

https://www.ronsplace.eu/Products/RonsHTMLCleaner

[SiLæncer]

Boostnote is an open-source note-taking app designed for programmers and web developers.

There are quick access links found on the lower right that include zoom, every type of document you could imagine, size, indent and last update. Resizing Boostnote smaller does screw up the formatting of these quick links. The menu section allows you to decide where your storage is, define hotkeys, and tweak the user interface.

Boostnote lets you take your notes in Markdown with live previewer, use snippet notes, multiple hotkeys, finder popup (similar to the spotlight of OSX), and latex support. Boostnote is a full featured note-taking app geared for programmers and web developers not to be confused with a post-it style application or a Notepad replacement.

License: Open Source

Changelog

Features:

Fix note title BoostIO/Boostnote#398
Adjust Note in Uitab && Add message notification for data policy save BoostIO/Boostnote#1025
Include each note only once when sorting by pin https://github.com/BoostIO/Boostnote/pull/1033
Added the context menu to the list view BoostIO/Boostnote#1036
Fix enabling no focus right click pin to top and show adequate context menu BoostIO/Boostnote#1038
Make ZZ work in vim mode BoostIO/Boostnote#1041
Added shortcut ctrl+q for quit and quit the app when using the Windows Close button BoostIO/Boostnote#1043
Only make the selected tag active BoostIO/Boostnote#1049
Add counter on note filter BoostIO/Boostnote#1052
Add PlantUML support BoostIO/Boostnote#1062
Enable importing file to empty folder BoostIO/Boostnote#1064
[Improvement] — Option for preferences in menus (916 & 1074) BoostIO/Boostnote#1093
Change default theme and add white BoostIO/Boostnote#1108
Add simple addon for CodeMirror BoostIO/Boostnote#1126
Add task item to indent adjustment target for list BoostIO/Boostnote#1127
Add community on tab in preferences BoostIO/Boostnote#1133
Add facebook group url to infotab BoostIO/Boostnote#1135
Icon Design Update BoostIO/Boostnote#1138
Improve the initial content BoostIO/Boostnote#1153
Update note design BoostIO/Boostnote#1161

Bug fixes:

Only decode the url when the content of the link is a string BoostIO/Boostnote#1042
Fix solarized dark/light code block thema bug BoostIO/Boostnote#1061
Solarized light/dark bug fix BoostIO/Boostnote#1081
Replace selection with pasted image BoostIO/Boostnote#1119
Fix windows scrolling bug BoostIO/Boostnote#1149

Dev:

Fix grunt pre-build error BoostIO/Boostnote#1104
Electron-prebuilt is obsolete. use latest electron instead BoostIO/Boostnote#1105
Removed mixpanel BoostIO/Boostnote#1114
Updated markdown-it-kbd to 1.1.1 from 1.1.0 BoostIO/Boostnote#115

[close]

https://boostnote.io/

[SiLæncer]

Highlight is a universal source code converter which transforms code to HTML, XHTML, RTF, LaTeX, TEX, SVG and BBCode files with syntax highlighting. (X)HTML and SVG output is formatted by CSS. It supports customizable color theme and language descriptions with regular expressions. The configuration files are Lua scripts with plug-in support. The tool contains several options to provide a consistent formatting of the output code.

License: Open Source

Changelog

Renamed examples directory to extras
Line anchors (-a) are attached as id attribute to the first span or li tag in
HTML output (https://github.com/andre-simon/highlight/issues/36)
Renamed ID prefix in outhtml_codefold plug-in to be compatible with -a IDs
Added fstab.lang and added anacrontab in filetypes.conf
Removed references to OutputType::HTML32
Added extras/css-themes and extras/langDefs-resources
(thanks to Tristano Ajmone)
CLI: removed deprecated indicator of --data-dir option
CLI: added --no-version-info option
GUI: fixed initial theme selection
GUI: added "Omit version info comment" option
GUI: added "Copy with MIME type" option for HTML output

[close]

http://www.andre-simon.de/

[SiLæncer]

Changelog

FIXED: Avoid triggering GC in fast if-then-else condition. If we do so we have to make sure to mark the `then' branch in GC, but the simplest seems to avoid GC in the first place. Also added an assertion that we are not in this position. Reported by Alan Baljeu.
DEBUG: Fix print_val() for summarised atoms
FIXED: cherry-pick of 4ffba6cc6648e1ef18165d0faf4995327965b25e needed more edit.
FIXED: exception/3 handling for undefined predicates if the predicate is locally defined rather than imported and thus the predicate id does not change. Breaks lazy loading of wordnet driver.

[close]

http://www.swi-prolog.org/

[SiLæncer]

Changelog

Features:

Fix note title BoostIO/Boostnote#398
store correct window size on Linux BoostIO/Boostnote#1144
Feature multiselect notes delete and move to another folder BoostIO/Boostnote#1070
fix anykey can close the initmodal window issue BoostIO/Boostnote#1176
Fix Margin at Note Detail BoostIO/Boostnote#1179
SideNavItem: add background when hover BoostIO/Boostnote#1180
Fix layout at initial modal BoostIO/Boostnote#1197
confirm tag at onBlur event BoostIO/Boostnote#1211
Correction Notification top-left BoostIO/Boostnote#1212
Add newsletter link to preference modal BoostIO/Boostnote#1226

Bug fix:

Fix surrogate pairs garbling on folded SideNav BoostIO/Boostnote#1184
Fix folded layout BoostIO/Boostnote#1202
Fixbug react code mirror BoostIO/Boostnote#1218
Fix finder layout BoostIO/Boostnote#1225

Dev:

React.PropTypes is deprecated from React 15.5 BoostIO/Boostnote#1113
fixed eslint warnings BoostIO/Boostnote#1170

[close]

https://boostnote.io/

[SiLæncer]

Easy CSS Menu lets you Easily create fantastic CSS-based drop down menus for your website. Many elegant menu templates are available, including modern glossy styles. Menus created with Easy CSS Menu Maker are very quick, compact and compatible with both modern and popular, but old web browsers. The menus created with Easy CSS Menu will also work on mobile and touch devices. What is more, they are search engine and SEO friendly. The code generated by Easy CSS Menu Maker is clean and can be easily used by expert web developers while automatic insertion features makes Easy CSS Menu Maker perfectly suitable for beginners. Generates valid CSS3 code.

Freeware

http://www.easycssmenu.com/

[SiLæncer]

Changelog

[Dec 12 2017]:
FIXED: retract/1: terminate with error if decompilation raises an error. Without, it is possible that retract/1 should logically succeed on a clause but skips the clause due to e.g., a resource exception.
[Dec 11 2017]:
FIXED: Race condition updating the frame generation and the notion of the global generation. Solution suggested by Keri Harris.
CLEANUP: Move global_generation() to pl-inline.h for all platforms for better readability.
TEST: Remove more concrete file names to allow tests to run concurrently.
TEST: Avoid hard-coded file names such that we can run the test from the same directory concurrently.
FIXED: Lowering the oldest_generation must be thread-safe. Spotted by Keri Harris.
FIXED: Dirty predicates activated while CGC is running must have their active generation updated.
FIXED: race condition for cleaning lingering data on predicates.
[Dec 10 2017]:
FIXED: If we push an accessible predicate while clause GC is active, we must update the generation if it is dirty.
DEBUG: Protect against recursive use of acquire_def()
FIXED: acquire_def() cannot be used recursively. Doing so in hashDefinition may lead to early release of indexes and clause references.
[Dec 9 2017]:
FIXED: Possible race extending referenced predicate dynamic array.
FIXED: Test for kill(), such that core dumps work after fatal signals are trapped.
[Dec 8 2017]:
FIXED: Could not build due to syntax error. Wouter Beek.
[Dec 7 2017]:
ADDED: PL_cvt_i_uint(), PL_cvt_i_ulong(), PL_cvt_i_uint64()
MODIFIED: PL_get_integer() no longer silently converts a float that happens to be integer into an integer if O_GMP is used. This is a remain from the days that floats were used as a poor mens replacement for large integers.
ENHANCED: On 64 bit machines we do not have to check bignums as these never fit an int.
ADDED: PL_cvt_i_uchar() and PL_cvt_i_ushort()
[Dec 6 2017]:
ADDED: PL_cvt_i_char() to accept one-character atoms, strings and lists
[Dec 5 2017]:
FIXED: open_string/2: double free if stream argument is instantiated.
[Dec 4 2017]:
FIXED: debug/1, nodebug/1: possible duplication of clauses when called at the same time from multiple threads. Wolfram Diestel.
[Dec 1 2017]:
FIXED: perform DCG and goal expansion if the result of term-expansion is a list.
FIXED: Find clauses if depth limit for deep indexing is exceeded. Jos de Roo.
[Nov 29 2017]:
ADDED: PL_cvt_i_char(), PL_cvt_i_short() and PL_cvt_i_int64(), extending Quintus/SICStus style native C conversions
Package http:
[Dec 1 2017]:
FIXED: Typo's in type documentation for `http_parameter/2'.
Package pengines:
[Dec 7 2017]:
FIXED: make sure that the variable names are also correct when the goal is being executed rather than only when the goal is being expanded.
Package plunit:
[Dec 11 2017]:
MODIFIED: Depth limit when printing failure terms from 10 to 100.
Package semweb:
[Dec 6 2017]:
ENHANCED: rdf_save/2: more efficient enumeration of subjects if a small graph from a large database is saved.
FIXED: Meta-predicate declaration for rdf_save_canonical_trig/2.

[close]

http://www.swi-prolog.org/

[SiLæncer]

ARGS is a program tool for making games with the look and feel of the '80s arcade games. Includes genres such as Run'n'Gun, vertical and horizontal Shooters or Platform games, you will be able to make similar games to Pac-Man, Commando, 1942, Ghosts 'n' Goblins or Gauntlet, all with your own sprite sheets, pixel art, sound effects and music.

Freeware

http://www.bruneras.com/arcadegamestudio/index.php

[SiLæncer]

Visual Studio Code is a powerful IDE, dedicated to building Web applications and cloud programs. The tool is a lightweight and resembles the functionality of Visual Studio, however it features comprehensive revision and compiling utilities, packed in a modern looking interface.

Freeware

Changelog

Bug fixes as well as community PRs still resulted in a great list of updates. Here are some of the release highlights:

Performance - Faster startup and other performance improvements.
Serviceability/Diagnostics - New VS Code diagnostics, logging, and extension monitoring.
Smarter IntelliSense - IntelliSense remembers your previous suggestion choices.
Better Tab layout - Tabbed headers can scale to fit the available space.
Git side-by-side image diff - Git source control provider can display image changes side by side.
Pipe output into VS Code - Easily view terminal output in a VS Code editor.
New debugging recipes - Learn how to debug Next.js, Meteor projects and applications using the nodemon utility.

[close]

https://code.visualstudio.com/

[SiLæncer]

PMD is a source code analyzer. It finds common programming flaws like unused variables, empty catch blocks, unnecessary object creation, and so forth. It supports Java, JavaScript, PLSQL, Apache Velocity, XML, XSL.
Additionally it includes CPD, the copy-paste-detector. CPD finds duplicated code in Java, C, C++, C#, PHP, Ruby, Fortran, JavaScript, PLSQL, Apache Velocity, Ruby, Scala, Objective C, Matlab, Python, Go, Swift.

Available Plugins include:

    Maven PMD.
    Eclipse.
    NetBeans.
    JBuilder.
    JDeveloper.
    IntelliJ IDEA.

PMD additionally includes CPD, the copy-paste-detector. CPD finds duplicated code in Java, C, C++, C#, PHP, Ruby, Fortran, JavaScript, PLSQL, Apache Velocity, Scala, Objective C, Matlab, Python, Go.

Open Source

Changelog

New Rule Designer:
Thanks to Clément Fournier, we now have a new rule designer GUI, which is based on JavaFX. It replaces the old designer and can be started via
bin/run.sh designer (on Unix-like platform such as Linux and Mac OS X)
bindesigner.bat (on Windows)
Java 9 support:
The Java grammar has been updated to support analyzing Java 9 projects:
private methods in interfaces are possible
The underscore “_” is considered an invalid identifier
Diamond operator for anonymous classes
The module declarations in module-info.java can be parsed
Concise try-with-resources statements are supported
Java 9 support is enabled by default. You can switch back to an older java version via the command line, e.g. -language java -version 1.8.
Revamped Apex CPD:
We are now using the Apex Jorje Lexer to tokenize Apex code for CPD. This change means:
All comments are now ignored for CPD. This is consistent with how other languages such as Java and Groovy work.
Tokenization honors the language specification, which improves accuracy.
CPD will therefore have less false positives and false negatives.
Java Type Resolution:
As part of Google Summer of Code 2017, Bendegúz Nagy worked on type resolution for Java. For this release he has extended support for method calls for both instance and static methods.
Method shadowing and overloading are supported, as are varargs. However, the selection of the target method upon the presence of generics and type inference is still work in progress. Expect it in forecoming releases.
As for fields, the basic support was in place for release 5.8.0, but has now been expanded to support static fields.
Metrics Framework:
As part of Google Summer of Code 2017, Clément Fournier is worked on the new metrics framework for object-oriented metrics.
There are already a couple of metrics (e.g. ATFD, WMC, Cyclo, LoC) implemented. More metrics are planned. Based on those metrics, rules like “GodClass” detection could be implemented more easily. The following rules benefit from the metrics framework: NcssCount (java), NPathComplexity (java), CyclomaticComplexity (both java and apex).
The Metrics framework has been abstracted and is available in pmd-core for other languages. With this PMD release, the metrics framework is supported for both Java and Apex.
Error Reporting:
A number of improvements on error reporting have taken place, meaning changes to some of the report formats.
Also of note, the xml report now provides a XML Schema definition, allowing easier parsing and validation.
Processing Errors:
Processing errors can now provide not only the message previously included on some reports, but also a full stacktrace. This will allow better error reports when providing feedback to the PMD team and help in debugging issues.
The report formats providing full stacktrace of errors are:
html
summaryhtml
textcolor
vbhtml
xml
Configuration Errors:
For a long time reports have been notified of configuration errors on rules, but they have remained hidden. On a push to make these more evident to users, and help them get the best results out of PMD, we have started to include them on the reports.
So far, only reports that include processing errors are showing configuration errors. In other words, the report formats providing configuration error reporting are:
csv
html
summaryhtml
text
textcolor
vbhtml
xml
As we move forward we will be able to detect and report more configuration errors (ie: incomplete auxclasspath) and include them to such reports.
Apex Rule Suppression:
Apex violations can now be suppressed very similarly to how it’s done in Java, by making use of a @SuppressWarnings annotation.
Supported syntax includes:
@SupressWarnings('PMD') // to supress all Apex rules
@SupressWarnings('all') // to supress all Apex rules
@SupressWarnings('PMD.ARuleName') // to supress only the rule named ARuleName
@SupressWarnings('PMD.ARuleName, PMD.AnotherRuleName') // to supress only the rule named ARuleName or AnotherRuleName
Rule Categories:
All built-in rules have been sorted into one of eight categories:
Best Practices: These are rules which enforce generally accepted best practices.
Code Style: These rules enforce a specific coding style.
Design: Rules that help you discover design issues.
Documentation: These rules are related to code documentation.
Error Prone: Rules to detect constructs that are either broken, extremely confusing or prone to runtime errors.
Multithreading: These are rules that flag issues when dealing with multiple threads of execution.
Performance: Rules that flag suboptimal code.
Security: Rules that flag potential security flaws.
These categories help you to find rules and figure out the relevance and impact for your project.
All rules have been moved accordingly, e.g. the rule “JumbledIncrementer”, which was previously defined in the ruleset “java-basic” has now been moved to the “Error Prone” category. The new rule reference to be used is <rule ref="category/java/errorprone.xml/JumbledIncrementer"/>.
The old rulesets like “java-basic” are still kept for backwards-compatibility but will be removed eventually. The rule reference documentation has been updated to reflect these changes.
New Rules:
The new Java rule NcssCount (category design) replaces the three rules “NcssConstructorCount”, “NcssMethodCount”, and “NcssTypeCount”. The new rule uses the metrics framework to achieve the same. It has two properties, to define the report level for method and class sizes separately. Constructors and methods are considered the same.
The new Java rule DoNotExtendJavaLangThrowable (category errorprone) is a companion for the java-strictexception.xml/DoNotExtendJavaLangError, detecting direct extensions of java.lang.Throwable.
The new Java rule ForLoopCanBeForeach (category errorprone) helps to identify those for-loops that can be safely refactored into for-each-loops available since java 1.5.
The new Java rule AvoidFileStream (category performance) helps to identify code relying on FileInputStream / FileOutputStream which, by using a finalizer, produces extra / unnecessary overhead to garbage collection, and should be replaced with Files.newInputStream / Files.newOutputStream available since java 1.7.
The new Java rule DataClass (category design) detects simple data-holders without behaviour. This might indicate that the behaviour is scattered elsewhere and the data class exposes the internal data structure, which breaks encapsulation.
The new Apex rule AvoidDirectAccessTriggerMap (category errorprone) helps to identify direct array access to triggers, which can produce bugs by either accessing non-existing indexes, or leaving them out. You should use for-each-loops instead.
The new Apex rule AvoidHardcodingId (category errorprone) detects hardcoded strings that look like identifiers and flags them. Record IDs change between environments, meaning hardcoded ids are bound to fail under a different setup.
The new Apex rule CyclomaticComplexity (category design) detects overly complex classes and methods. The report threshold can be configured separately for classes and methods.
A whole bunch of new rules has been added to Apex. They all fit into the category errorprone. The 5 rules are migrated for Apex from the equivalent Java rules and include:
EmptyCatchBlock to detect catch blocks completely ignoring exceptions.
EmptyIfStmt for if blocks with no content, that can be safely removed.
EmptyTryOrFinallyBlock for empty try / finally blocks that can be safely removed.
EmptyWhileStmt for empty while loops that can be safely removed.
EmptyStatementBlock for empty code blocks that can be safely removed.
The new Apex rule AvoidSoslInLoops (category performance) is the companion of the old AvoidSoqlInLoops rule, flagging SOSL (Salesforce Object Search Language) queries when within loops, to avoid governor issues, and hitting the database too often.
Modified Rules:
The Java rule UnnecessaryFinalModifier (category codestyle, former ruleset java-unnecessarycode) has been merged into the rule UnnecessaryModifier. As part of this, the rule has been revamped to detect more cases. It will now flag anonymous class’ methods marked as final (can’t be overridden, so it’s pointless), along with final methods overridden / defined within enum instances. It will also flag final modifiers on try-with-resources.
The Java rule UnnecessaryParentheses (category codestyle, former ruleset java-controversial) has been merged into UselessParentheses (category codestyle, former ruleset java-unnecessary). The rule covers all scenarios previously covered by either rule.
The Java rule UncommentedEmptyConstructor (category documentation, former ruleset java-design) will now ignore empty constructors annotated with javax.inject.Inject.
The Java rule AbstractClassWithoutAnyMethod (category bestpractices, former ruleset java-design) will now ignore classes annotated with com.google.auto.value.AutoValue.
The Java rule GodClass (category design', former ruleset java-design`) has been revamped to use the new metrics framework.
The Java rule LooseCoupling (category bestpractices, former ruleset java-coupling) has been replaced by the typeresolution-based implementation.
The Java rule CloneMethodMustImplementCloneable (category errorprone, former ruleset java-clone) has been replaced by the typeresolution-based implementation and is now able to detect cases if a class implements or extends a Cloneable class/interface.
The Java rule UnusedImports (category bestpractices, former ruleset java-imports) has been replaced by the typeresolution-based implementation and is now able to detect unused on-demand imports.
The Java rule SignatureDeclareThrowsException (category design, former ruleset ‘java-strictexception’) has been replaced by the typeresolution-based implementation. It has a new property IgnoreJUnitCompletely, which allows all methods in a JUnit testcase to throw exceptions.
The Java rule NPathComplexity (category design, former ruleset java-codesize) has been revamped to use the new metrics framework. Its report threshold can be configured via the property reportLevel, which replaces the now deprecated property minimum.
The Java rule CyclomaticComplexity (category design, former ruleset java-codesize) has been revamped to use the new metrics framework. Its report threshold can be configured via the properties classReportLevel and methodReportLevel separately. The old property reportLevel, which configured the level for both total class and method complexity, is deprecated.
The Java rule CommentRequired (category documentation, former ruleset java-comments) has been revamped to include 2 new properties:
accessorCommentRequirement to specify documentation requirements for getters and setters (default to ignored)
methodWithOverrideCommentRequirement to specify documentation requirements for methods annotated with @Override (default to ignored)
The Java rule EmptyCatchBlock (category errorprone, former ruleset java-empty) has been changed to ignore exceptions named ignore or expected by default. You can still override this behaviour by setting the allowExceptionNameRegex property.
The Java rule OptimizableToArrayCall (category performance, former ruleset design) has been modified to fit for the current JVM implementations: It basically detects now the opposite and suggests to use Collection.toArray(new E[0]) with a zero-sized array. See Arrays of Wisdom of the Ancients.
Deprecated Rules:
The Java rules NcssConstructorCount, NcssMethodCount, and NcssTypeCount (ruleset java-codesize) have been deprecated. They will be replaced by the new rule NcssCount in the category design.
The Java rule LooseCoupling in ruleset java-typeresolution is deprecated. Use the rule with the same name from category bestpractices instead.
The Java rule CloneMethodMustImplementCloneable in ruleset java-typeresolution is deprecated. Use the rule with the same name from category errorprone instead.
The Java rule UnusedImports in ruleset java-typeresolution is deprecated. Use the rule with the same name from category bestpractices instead.
The Java rule SignatureDeclareThrowsException in ruleset java-typeresolution is deprecated. Use the rule with the same name from category design instead.
The Java rule EmptyStaticInitializer in ruleset java-empty is deprecated. Use the rule EmptyInitializer from the category errorprone, which covers both static and non-static empty initializers.`
The Java rules GuardDebugLogging (ruleset java-logging-jakarta-commons) and GuardLogStatementJavaUtil (ruleset java-logging-java) have been deprecated. Use the rule GuardLogStatement from the category bestpractices, which covers all cases regardless of the logging framework.
Removed Rules:
The deprecated Java rule UseSingleton has been removed from the ruleset java-design. The rule has been renamed long time ago to UseUtilityClass (category design).
Java Symbol Table:
A bug in symbol table prevented the symbol table analysis to properly match primitive arrays types. The issue affected the java-unsedcode/UnusedPrivateMethod rule, but other rules may now produce improved results as consequence of this fix.
Apex Parser Update:
The Apex parser version was bumped, from 1.0-sfdc-187 to 210-SNAPSHOT. This update let us take full advantage of the latest improvements from Salesforce, but introduces some breaking changes:
BlockStatements are now created for all control structures, even if no brace is used. We have therefore added a hasCurlyBrace method to differentiate between both scenarios.
New AST node types are available. In particular CastExpression, ConstructorPreamble, IllegalStoreExpression, MethodBlockStatement, Modifier, MultiStatement, NestedExpression, NestedStoreExpression, NewKeyValueObjectExpression and StatementExecuted
Some nodes have been removed. Such is the case of TestNode, DottedExpression and NewNameValueObjectExpression (replaced by NewKeyValueObjectExpression)
All existing rules have been updated to reflect these changes. If you have custom rules, be sure to update them.
For more info about the included Apex parser, see the new pmd module “pmd-apex-jorje”, which packages and provides the parser as a binary.
Incremental Analysis:
The incremental analysis feature first introduced in PMD 5.6.0 has been enhanced. A few minor issues have been fixed, and several improvements have been performed to make it more accurate.
The cache will now detect changes to the JARs referenced in the auxclasspath instead of simply looking at their paths and order. This means that if you are referencing a JAR you are overwriting in some way, the incremental analysis can now detect it and invalidate it’s cache to avoid false reports.
Similarly, any changes to the execution classpath of PMD will invalidate the cache. This means that if you have custom rules packaged in a jar, any changes to it will invalidate the cache automatically.
We have also improved logging on the analysis code, allowing better insight into how the cache is performing, under debug / verbose builds you can even see individual hits / misses to the cache (and the reason for any miss!)
Finally, as this feature keeps maturing, we are gently pushing this forward. If not using incremental analysis, a warning will now be produced suggesting users to adopt it for better performance.
Rule and Report Properties:
The implementation around the properties support for rule properties and report properties has been revamped to be fully typesafe. Along with that change, the support classes have been moved into an own package net.sourceforge.pmd.properties. While there is no change necessary in the ruleset XML files, when using/setting values for rules, there are adjustments necessary when declaring properties in Java-implemented rules.
Rule properties can be declared both for Java based rules and XPath rules. This is now very well documented in Working with properties.
With PMD 6.0.0, multivalued properties are now also possible with XPath rules.
Fixed Issues:
#394: [core] PMD exclude rules are failing with IllegalArgumentException with non-default minimumPriority
#532: [core] security concerns on URL-based rulesets
#538: [core] Provide an XML Schema for XML reports
#600: [core] Nullpointer while creating cache File
#604: [core] Incremental analysis should detect changes to jars in classpath
#608: [core] Add DEBUG log when applying incremental analysis
#618: [core] Incremental Analysis doesn’t close file correctly on Windows upon a cache hit
#643: [core] PMD Properties (dev-properties) breaks markup on CodeClimateRenderer
#680: [core] Isolate classloaders for runtime and auxclasspath
#762: [core] Remove method and file property from available property descriptors for XPath rules
#763: [core] Turn property descriptor util into an enum and enrich its interface
apex
#265: [apex] Make Rule suppression work
#488: [apex] Use Apex lexer for CPD
#489: [apex] Update Apex compiler
#500: [apex] Running through CLI shows jorje optimization messages
#605: [apex] java.lang.NoClassDefFoundError in the latest build
#637: [apex] Avoid SOSL in loops
#760: [apex] EmptyStatementBlock complains about missing rather than empty block
#766: [apex] Replace old Jorje parser with new one
#768: [apex] java.lang.NullPointerException from PMD
cpp
#448: [cpp] Write custom CharStream to handle continuation characters
java
#1454: [java] OptimizableToArrayCall is outdated and invalid in current JVMs
#1513: [java] Remove deprecated rule UseSingleton
#328: [java] java.lang.ClassFormatError: Absent Code attribute in method that is not native or abstract in class file javax/servlet/jsp/PageContext
#487: [java] Fix typeresolution for anonymous extending object
#496: [java] processing error on generics inherited from enclosing class
#510: [java] Typeresolution fails on a simple primary when the source is loaded from a class literal
#527: [java] Lombok getter annotation on enum is not recognized correctly
#534: [java] NPE in MethodTypeResolution for static methods
#603: [core] incremental analysis should invalidate upon Java rule plugin changes
#650: [java] ProcesingError analyzing code under 5.8.1
#732: [java] LinkageError with aux classpath
java-basic
#565: [java] False negative on DontCallThreadRun when extending Thread
java-comments
#396: [java] CommentRequired: add properties to ignore @Override method and getters / setters
#536: [java] CommentDefaultAccessModifierRule ignores constructors
java-controversial
#388: [java] controversial.AvoidLiteralsInIfCondition 0.0 false positive
#408: [java] DFA not analyzing asserts
#537: [java] UnnecessaryParentheses fails to detect obvious scenario
java-design
#357: [java] UncommentedEmptyConstructor consider annotations on Constructor
#438: [java] Relax AbstractClassWithoutAnyMethod when class is annotated by @AutoValue
#590: [java] False positive on MissingStaticMethodInNonInstantiatableClass
java-logging * #457: [java] Merge all log guarding rules * #721: [java] NPE in PMD 5.8.1 InvalidSlf4jMessageFormat
java-sunsecure
#468: [java] ArrayIsStoredDirectly false positive
java-unusedcode
#521: [java] UnusedPrivateMethod returns false positives with primitive data type in map argument
java-unnecessarycode
#412: [java] java-unnecessarycode/UnnecessaryFinalModifier missing cases
#676: [java] java-unnecessarycode/UnnecessaryFinalModifier on try-with-resources

API Changes:

The class net.sourceforge.pmd.lang.dfa.NodeType has been converted to an enum. All node types are enum members now instead of int constants. The names for node types are retained.
The Properties API (rule and report properties) has been revamped to be fully typesafe. This is everything around net.sourceforge.pmd.properties.PropertyDescriptor.
Note: All classes related to properties have been moved into the package net.sourceforge.pmd.properties.
The rule classes net.sourceforge.pmd.lang.apex.rule.apexunit.ApexUnitTestClassShouldHaveAsserts and net.sourceforge.pmd.lang.apex.rule.apexunit.ApexUnitTestShouldNotUseSeeAllDataTrue have been renamed to ApexUnitTestClassShouldHaveAssertsRule and ApexUnitTestShouldNotUseSeeAllDataTrueRule, respectively. This is to comply with the naming convention, that each rule class should be suffixed with “Rule”.
This change has no impact on custom rulesets, since the rule names themselves didn’t change.
The never implemented method PMD.processFiles(PMDConfiguration, RuleSetFactory, Collection<File>, RuleContext, ProgressMonitor) along with the interface ProgressMonitor has been removed.
The method PMD.setupReport(RuleSets, RuleContext, String) is gone. It was used to report dysfunctional rules. But PMD does this now automatically before processing the files, so there is no need for this method anymore.

All APIs deprecated in older versions are now removed. This includes:

Renderer.getPropertyDefinitions
AbstractRenderer.defineProperty(String, String)
AbstractRenderer.propertyDefinitions
ReportListener
Report.addListener(ReportListener)
SynchronizedReportListener
CPDConfiguration.CPDConfiguration(int, Language, String)
CPDConfiguration.getRendererFromString(String)
StreamUtil
StringUtil.appendXmlEscaped(StringBuilder, String)
StringUtil.htmlEncode(String)
Several methods in net.sourceforge.pmd.util.CollectionUtil have been deprecated and will be removed in PMD 7.0.0. In particular:
CollectionUtil.addWithoutDuplicates(T[], T)
CollectionUtil.addWithoutDuplicates(T[], T[])
CollectionUtil.areSemanticEquals(T[], T[])
CollectionUtil.areEqual(Object, Object)
CollectionUtil.arraysAreEqual(Object, Object)
CollectionUtil.valuesAreTransitivelyEqual(Object[], Object[])
Several methods in net.sourceforge.pmd.util.StringUtil have been deprecated and will be removed in PMD 7.0.0. In particular:
StringUtil.startsWithAny(String, String[])
StringUtil.isNotEmpty(String)
StringUtil.isEmpty(String)
StringUtil.isMissing(String)
StringUtil.areSemanticEquals(String, String)
StringUtil.replaceString(String, String, String)
StringUtil.replaceString(String, char, String)
StringUtil.substringsOf(String, char)
StringUtil.substringsOf(String, String)
StringUtil.asStringOn(StringBuffer, Iterator, String)
StringUtil.asStringOn(StringBuilder, Object[], String)
StringUtil.lpad(String, int)
The class net.sourceforge.pmd.lang.java.typeresolution.typedefinition.JavaTypeDefinition is now abstract, and has been enhanced to provide several new methods.
The constructor of net.sourceforge.pmd.RuleSetFactory, which took a ClassLoader is deprecated. Please use the alternative constructor with the net.sourceforge.pmd.util.ResourceLoader instead.
The following GUI related classes have been deprecated and will be removed in PMD 7.0.0. The tool “bgastviewer”, that could be started via the script bgastviewer.bat or run.sh bgastviewer is deprecated, too, and will be removed in PMD 7.0.0. Both the “old designer” and “bgastviewer” are replaced by the New Rule Designer.
net.sourceforge.pmd.util.designer.CodeEditorTextPane
net.sourceforge.pmd.util.designer.CreateXMLRulePanel
net.sourceforge.pmd.util.designer.Designer
net.sourceforge.pmd.util.designer.DFAPanel
net.sourceforge.pmd.util.designer.LineGetter
net.sourceforge.pmd.util.viewer.Viewer
net.sourceforge.pmd.util.viewer.gui.ActionCommands
net.sourceforge.pmd.util.viewer.gui.ASTPanel
net.sourceforge.pmd.util.viewer.gui.EvaluationResultsPanel
net.sourceforge.pmd.util.viewer.gui.MainFrame
net.sourceforge.pmd.util.viewer.gui.ParseExceptionHandler
net.sourceforge.pmd.util.viewer.gui.SourceCodePanel
net.sourceforge.pmd.util.viewer.gui.XPathPanel
net.sourceforge.pmd.util.viewer.gui.menu.ASTNodePopupMenu
net.sourceforge.pmd.util.viewer.gui.menu.AttributesSubMenu
net.sourceforge.pmd.util.viewer.gui.menu.SimpleNodeSubMenu
net.sourceforge.pmd.util.viewer.gui.menu.XPathFragmentAddingItem
net.sourceforge.pmd.util.viewer.model.ASTModel
net.sourceforge.pmd.util.viewer.model.AttributeToolkit
net.sourceforge.pmd.util.viewer.model.SimpleNodeTreeNodeAdapter
net.sourceforge.pmd.util.viewer.model.ViewerModel
net.sourceforge.pmd.util.viewer.model.ViewerModelEvent
net.sourceforge.pmd.util.viewer.model.ViewerModelListener
net.sourceforge.pmd.util.viewer.util.NLS
The following methods in net.sourceforge.pmd.Rule have been deprecated and will be removed in PMD 7.0.0. All methods are replaced by their bean-like counterparts
void setUsesDFA(). Use void setDfa(boolean) instead.
boolean usesDFA(). Use boolean isDfa() instead.
void setUsesTypeResolution(). Use void setTypeResolution(boolean) instead.
boolean usesTypeResolution(). Use boolean isTypeResolution() instead.
void setUsesMultifile(). Use void setMultifile(boolean) instead.
boolean usesMultifile(). Use boolean isMultifile() instead.
boolean usesRuleChain(). Use boolean isRuleChain() instead.

External Contributions:

#287: [apex] Make Rule suppression work - Robert Sösemann
#420: [java] Fix UR anomaly in assert statements - Clément Fournier
#482: [java] Metrics testing framework + improved capabilities for metrics - Clément Fournier
#484: [core] Changed linux usage to a more unix like path - patriksevallius
#486: [java] Add basic method typeresolution - Bendegúz Nagy
#492: [java] Typeresolution for overloaded methods - Bendegúz Nagy
#495: [core] Custom rule reinitialization code - Clément Fournier
#479: [core] Typesafe and immutable properties - Clément Fournier
#499: [java] Metrics memoization tests - Clément Fournier
#501: [java] Add support for most specific vararg method type resolution - Bendegúz Nagy
#502: [java] Add support for static field type resolution - Bendegúz Nagy
#505: [java] Followup on metrics - Clément Fournier
#506: [java] Add reduction rules to type inference - Bendegúz Nagy
#511: [core] Prepare abstraction of the metrics framework - Clément Fournier
#512: [java] Add incorporation to type inference - Bendegúz Nagy
#513: [java] Fix for maximally specific method selection - Bendegúz Nagy
#514: [java] Add static method type resolution - Bendegúz Nagy
#517: [doc] Metrics documentation - Clément Fournier
#518: [core] Properties refactoring: factorized enumerated property - Clément Fournier
#523: [java] Npath complexity metric and rule - Clément Fournier
#524: [java] Add support for explicit type arguments with method invocation - Bendegúz Nagy
#525: [core] Fix line ending and not ignored files issues - Matias Comercio
#528: [core] Fix typo - Ayoub Kaanich
#529: [java] Abstracted the Java metrics framework - Clément Fournier
#530: [java] Fix issue #527: Lombok getter annotation on enum is not recognized correctly - Clément Fournier
#533: [core] improve error message - Dennis Kieselhorst
#535: [apex] Fix broken Apex visitor adapter - Clément Fournier
#542: [java] Metrics abstraction - Clément Fournier
#545: [apex] Apex metrics framework - Clément Fournier
#548: [java] Metrics documentation - Clément Fournier
#550: [java] Add basic resolution to type inference - Bendegúz Nagy
#553: [java] Refactored ParserTst into a static utility class + add getSourceFromClass - Clément Fournier
#554: [java] Fix #537: UnnecessaryParentheses fails to detect obvious scenario - Clément Fournier
#555: [java] Changed metrics/CyclomaticComplexityRule to use WMC when reporting classes - Clément Fournier
#556: [java] Fix #357: UncommentedEmptyConstructor consider annotations on Constructor - Clément Fournier
#557: [java] Fix NPath metric not counting ternaries correctly - Clément Fournier
#563: [java] Add support for basic method type inference for strict invocation - Bendegúz Nagy
#566: [java] New rule in migrating ruleset: ForLoopCanBeForeach - Clément Fournier
#567: [java] Last API change for metrics (metric options) - Clément Fournier
#570: [java] Model lower, upper and intersection types - Bendegúz Nagy
#573: [java] Data class rule - Clément Fournier
#576: [doc][java] Add hint for Guava users in InefficientEmptyStringCheck - mmoehring
#578: [java] Refactored god class rule - Clément Fournier
#579: [java] Update parsing to produce upper and lower bounds - Bendegúz Nagy
#580: [core] Add AbstractMetric to topple the class hierarchy of metrics - Clément Fournier
#581: [java] Relax AbstractClassWithoutAnyMethod when class is annotated by @AutoValue - Niklas Baudy
#583: [java] Documentation about writing metrics - Clément Fournier
#585: [java] Moved NcssCountRule to codesize.xml - Clément Fournier
#587: [core] Properties refactoring: Move static constants of ValueParser to class ValueParserConstants - Clément Fournier
#588: [java] XPath function to compute metrics - Clément Fournier
#598: [java] Fix #388: controversial.AvoidLiteralsInIfCondition 0.0 false positive - Clément Fournier
#602: [java] [apex] Separate multifile analysis from metrics - Clément Fournier
#620: [core] Moved properties to n.s.pmd.properties - Clément Fournier
#625: [apex] empty code ruleset for apex - Jan Aertgeerts
#632: [apex] Add AvoidDirectAccessTriggerMap rule to the style set - Jan Aertgeerts
#644: [core] Prevent internal dev-properties from being displayed on CodeClimate renderer - Filipe Esperandio
#660: [apex] avoid sosl in loops - Jan Aertgeerts
#661: [apex] avoid hardcoding id’s - Jan Aertgeerts
#666: [java] Add DoNotExtendJavaLangThrowable rule - Robert Painsi
#668: [core] Fix javadoc warnings on pmd-core - Clément Fournier
#669: [core] Builder pattern for properties - Clément Fournier
#675: [java] Fix in Java grammar: Try with final resource node error - Gonzalo Ibars Ingman
#679: [core] Token scheme generalization - Gonzalo Ibars Ingman
#694: [core] Add minor fixes to root pom - Matias Comercio
#696: [core] Add remove operation over nodes - Matias Comercio
#711: [ui] New rule designer - Clément Fournier
#722: [java] Move NPathComplexity from metrics to design - Clément Fournier
#723: [core] Rule factory refactoring - Clément Fournier
#726: [java] Fix issue #721 (NPE in InvalidSlf4jMessageFormat) - Clément Fournier
#727: [core] Fix #725: numeric property descriptors now check their default value - Clément Fournier
#733: [java] Some improvements to CommentRequired - Clément Fournier
#734: [java] Move CyclomaticComplexity from metrics to design - Clément Fournier
#736: [core] Make Saxon support multi valued XPath properties - Clément Fournier
#737: [doc] Fix NPathComplexity documentation bad rendering - Clément Fournier
#744: [doc] Added Apex to supported languages - Michał Kuliński
#746: [doc] Fix typo in incremental analysis log message - Clément Fournier
#749: [doc] Update the documentation for properties - Clément Fournier
#758: [core] Expose the full mapping from property type id to property extractor - Clément Fournier
#764: [core] Prevent method and file property use in XPath rules - Clément Fournier
#771: [apex] Fix Apex metrics framework failing on triggers, refs #768 - Clément Fournier
#774: [java] Avoid using FileInput/Output - see JDK-8080225 - Chas Honton

[close]

https://pmd.github.io/

[SiLæncer]

Nightcode is a handy integrated development environment that is aimed at programmers who are looking for a tool that can help them with projects written in Clojure or Java. With it you are able to create console, Android, iOS, .NET, desktop, web and graphics applications, as well as write code that is to be used in games.

Freeware

Release Notes

This release updates Nightcode and all the built-in templates to use Clojure 1.9! I also tried my best to make the templates work with Java 9 (I think the only one that doesn't is the graphics template, but the issue appears to only be fixable in the quil library itself).

[close]

https://sekao.net/nightcode/

[SiLæncer]

Visual Studio Code is a powerful IDE, dedicated to building Web applications and cloud programs. The tool is a lightweight and resembles the functionality of Visual Studio, however it features comprehensive revision and compiling utilities, packed in a modern looking interface.

Freeware

Changelog

Update addresses these issues:

code --status doesn't work if your shell is PowerShell
Every time i lunch code it starts with code-stdin-randomchars.txt file
Task ${relativeFile} slash style
Git diff not working for UNC paths
what is "Would you like to enable auto fetching of Git repositories?" bug
Type error: cannot read property comments of null
Git doesn't pick up user installation directories

[close]

https://code.visualstudio.com/

[SiLæncer]

Changelog

FIXED: Errornous calls to new setGenerationFrame().
PORT: install TeX fonts for generating plaintext manual.
ENHANCED: library(nb_set): avoid cyclic term error when compiled with occurs check set to error.
DEBUG: Fixed consistency check in nextClause__LD().
MODIFIED: current_atom/1 no longer returns the reserved atom '<garbage_collected>'. This atom blocks internal consistency checks.
DEBUG: make -d chk_secure work again.
TEST: findnsols/4 AGC interaction.
FIXED: findnsols/4: prevent early release of findall bag, causing a crash in AGC. Found by Wouter Beek.
TEST: Make save state tests run on Windows.
TEST: Avoid loading library(limit) if the shared object does not exist.
CLEANUP: format/3 and friends: avoid start/endCritical to allow for signal processing and move Slock() to the wrapper to make its use obviously correct.
FIXED: Avoid critical regions to stop processing fatal signals such as SEGV. Synchronous handling of such signals in Prolog leads to a signal handling loop.
TEST: Allow save-program tests to run concurrently by avoiding fixed file names.
CLEANUP: variant/2: Avoid copying inunstantiated data. Although benign, the old implementation leads to messages from debugging tools and performs unnecessary work.
FIXED: markAccessedPredicates() did not use atomic management of the last access generation.
FIXED: mistakes in previous commit
FIXED: Race conditions establishing the generation at which a predicate is about to be accessed for retract/1, retractall/1, clause/2 and nth_clause/3. May lead to accessing freed clauses, typically causing a crash.
CLEANUP: retract/1: remove start/endCritical() calls. They are no longer needed and were not properly balanced.
CLEANUP: gcClauseRefs() can be static in pl-proc.c
FIXED: race condition when adding a fresh atom to a bucket while rehashing is in progress that may cause the bucket to become corrupted
FIXED: Use UTF-8 encoding for CLP(FD) source code, closing #281. Without this directive, you may get warnings when CLP(FD) is used in non-UTF8 environments.
Now, library(clpfd) is loaded without warnings also with LANG=C.
PORT: Provide fallback for sigCrashHandler()
PORT: Win32: pthread_setname_np() is a stub in some versions of the winpthread library. Avoid it.
CLEANUP: Avoid compiler warnings
PORT: Updated build instructions for Ubuntu 17.10
TEST: Added test case used for tracking AGC issue
CLEANUP: marking atoms
FIXED: Possibility that atoms are not marked for GC. With Keri Harris.
DEBUG: More atom debugging stuff
DEBUG: Make -DO_DEBUG_ATOMGC work again.
ENHANCED: Avoid looping when catching a fatal signal in foreign
extensions. Now tries: get back to Prolog using a longjmp(). Note that this may leak resources. If that fails, try to print a stack trace and exit. Abramo Bagnara.
FIXED: mutex_statistics/0 printing wrong value for lock count if the
utex is locked (this predicate only supports analysis of performance issues in multi-threaded applications).
MODIFIED: Exit with status 4 when using 'e' from the debugger.
Indicate exit status on the terminal with exitting from the debugger and system errors.
DOC: wrong arity for thread_join/1, so it doesn't show up in the manual completion.
TEST: Make test thread_agc_findall.pl both test different and equal prefixes, stressing AGC better.
TEST: Do not considet queue_gc tests failing to reclaim the queues a fatal test failure. This just can happen.

Package clib:

TEST: library(process): make test suite test availability of programs.
MODIFIED: open_memory_file/3,4 to use POSIX newlines on all platforms.
FIXED: chmod/2 for Windows to use _wchmod().
CLEANUP: remove unused winsock code
PORT: winsock rewrite to bring Windows socket code in line with POSIX socket code
PORT: use correct winsock error codes
ENHANCED: support blocking UDP sockets
FIXED: enable signals to be handled when send() blocks on a partially-full TCP buffer
FIXED: typo it -> in

Package cpp:

CLEANUP: Update links to manual tools

[close]

http://www.swi-prolog.org/