calls be omitted from the recorded profile

files now follows POSIX shells (at least on a

Unix-alike), so the first treats empty environment variables as

set and the second does not.  Previously both ignored empty

variables.  There are several uses of the first form in

warnings or messages that inherit from particular classes.

Based on patch from Lionel Henry submitted with

terminals.  Line editing is possible when command

normalizes case of long names of path elements in case-insensitive

supports UTF-8 file names with characters

that cannot be translated to the native encoding (

specify the workspace to be restored.  This allows equals to be

NumLock on.  Tilde can be pasted with an Italian keyboard

falls back to copying when junction creation fails during

package checking (patch from Duncan Murdoch).

But portable code should not rely on this.)

The deprecated support for specifying C++98 for package

Either PCRE2 or PCRE1 >= 8.32 (Nov 2012) is required: the

deprecated provision for 8.20--8.31 has been removed.

3.6.0.  Neither are part of the API, but packages using

10 enforces the distinction between scalars

establishing a calling handler in C code for conditions inheriting

used for compiling packages (including base packages).

for checking consistency of BLAS/LAPACK/LINPACK calls --- see

A C++ compiler default is set only if the C++11 standard is

supported: it no longer falls back to C++98.

PCRE2 is used if available.  To make use of PCRE1 if PCRE2

can be rebuilt from the tarball created by

the source files are properly cleaned by

instructing the tester to do so.  This can be temporarily

circumvented during development by setting environment variable

There is the beginnings of support for the recently approved

C++20 standard, specified analogously to C++14 and C++17.  There is

currently only limited support for this in compilers, with flags

is deprecated now.  Such use has been rare, and has

as expected in some cases only.  In other cases, wrong

silently been truncated, not detecting previous errors.

Long-standing issue where the X11 device could lose events