URI module support for IRIs (RFC 3987).
• IRIs are just like URIs but characters with codes above 127 are allows (they are disallowed in URIs by RFC 3986).
• (net.uri:string-to-iri string) returns an instance of net.uri:iri.
• (net.uri:iri-to-string iri) returns the string representation of iri, which must be an instances of net.uri:iri.

(net.uri:uri-host (net.uri:parse-uri "http://test#"))

Defined a client-cache object that works with do-http-request to save HTTP responses and in the future use those saved responses rather than go out to the network to fetch responses.

Ensure that multiple users of the same cookie-jar do not interfere with each other.

When SSL was specified as T or a certificate, temporary redirect was performed correctly to https, but when specified with a context (as created via socket:make-ssl-client-context) object the redirection was incorrectly set to http. This patch ensures correct temporary redirection in all SSL cases.

parse-uri has been modified, for parsing the query of a URI, to not decode #+, #= and #& if they are percent encoded. This means %2b, for example, will not be converted to `+'. This is contrary to RFC 3986, but otherwise there is no way to pass these characters as field values.

parse-uri/render-uri and string-to-uri/uri-to-string are pairs which should be used together. Mixing usage on the same URI object will result in confusion.

• string-to-uri string:  Parse STRING as a URI and either signal an error if it cannot be parsed or return the URI object. This function differs from parse-uri in that the query is not decoded. The knowledge of how to properly decode the query is outside the bounds of RFC 3986.
• uri-to-string uri:  The inverse of string-to-uri, which returns the string representation of URI.

Non-strict parse allows #space in queries and double slashes at the start of the path are reduced to a single slash (http://foo.com//bar is parsed as http://foo.com/bar, in non-strict mode).

render-uri works in an upper-case modes.

merge-uris has been brought into conformance with RFC3986, mostly having to do with leading . and ..'s in path elements.

parse-uri no longer canonicalizes away a path of "/". That is, with this patch, this is no longer true:

(uri= (parse-uri "http://foo.com/") (parse-uri "http://foo.com"))

The CG patch (pkk006.001) and the IDE patch (pkl001.001) are both needed for the complete improvements.

If multiple windows have errors in their custom redisplay-window methods, confusion could result if the error for the first window is being handled and then a repaint message for the second window is handled. The error dialog may not appear or respond, and the IDE listener could be left unresponsive. On the GTK platforms, other windows could also fail to redraw, even after throwing out of the error. This patch corrects the problem.

• 3.1.0: Add the capability of making client server connections encrypted. See the :authenticate and :rsa-keys argumments to start-server and the :secure argument to open-network-database.
• 3.1.1: An expression cursor over a class will now be returned even if no member of the class has been created yet. The database must be read/write for this to work.

New routines excl:nice-signal-name and excl.osi:strsignal.

excl:nice-signal-name returns a "nice" name for signal-number, an integer. This nice name is operating system dependent. For example, on Solaris and Linux, (nice-signal-name 1) returns "Hangup". On FreeBSD and macOS, the same thing returns "Hangup: 1". If signal-number does not name a valid signal, then nil is returned.

excl.osi:strsignal is an alias for excl:nice-signal-name, and parallels the UNIX library function strsignal().

As a side note, code/osi.005 was accidentally skipped, so it is included here as an empty stub that allows osi.006 to be loaded via require.

Fixes a bug in which the fasl reader fails to allow for surrogate pairs. Strings in fasl files are written as utf-8, which means that surrogate pairs are normally left out. But because we also extended the utf-8 external-format, they are nevertheless handled and encoded in a pseudo-standard way. With this patch the shared-library has now been updated to enhance the fasl-reader to match the utf-8 external format so that it will read these surrogate pairs captured in string constants.

Additionally, in smp a lisp thread can block garbage collection indefinitely by spending a long time in a foreign call that disallows gc, or in a long-running loop compiled with high speed and low safety settings. A bug in such lisp or foreign code could block the lisp forever since almost no lisp interaction with the external world can take place without allocating something.

The garbage collector had a timeout that would kill the lisp with an error message if it found it had been blocked for what seemed like an excessive amount of time, so that the user could investigate the problem. We found cases of legitimate programs that took arbitrarily long to finish, so we've disabled the timeout failure.

The loop macro inspired a new method of associating forms appearing in files with implementational forms. For example, in the loop phrase `for i below 10', the user could specify the :pos argument to the :break command to specify the `below' keyword (or just click on the keyword itself while in the stepper dialog of the ide), and the breakpoint would be automatically associated with the form implementing the keyword (in this case, a (< i 10) test).

This patch fixes associations between loop keywords and their underlying forms, and adds a few more associations. Specifically, the `collect' keyword was associated with the final return of the collected list, rather than the adding of each result to the collected list within each iteration. Also, some arithmetic for iterations have been made more intuitive in how they are associated with their implementations. Finally, the loop keywords across, in, and in-sequence (an Allegro CL enhancement) now have associations where there were none before.

This patch changes the :ssl module to load dynamically linked OpenSSL libraries. As a result, OpenSSL updates will no longer require an ACL patch or update. This change will be transparent to many users of SSL, but some will need to modify their environment or their code to continue using SSL features.

If (require :ssl) signals openssl-load-error, then it will be necessary to specify the location of the OpenSSL shared libraries.

Most UNIX machines use the environment variable LD_LIBRARY_PATH to tell programs where to look for shared libraries. Mac OS X uses the variable DYLD_LIBRARY_PATH. Consult your operating system documentation for details on what you should use.

On Windows, this patch changes nothing. Note: the method of loading the SSL libraries has always been dynamic on Windows, but we have been the supplier of those binaries. See the readme.txt for more details on the binaries we distribute and how to use them.

In all cases, it is now the responsibility of the user to maintain a suitable set of OpenSSL shared libraries. In general, on machines with production software, those libraries will be part of operating system updates.

See the updated on-line documentation for details.

Windows users, please read the OpenSSL readme.txt for installation instructions.

Windows users, please read the OpenSSL readme.txt for installation instructions.