Fixes a bug in the build of the library that prevents it from being startable in MacOSX 10.4. Users planning on upgrading from 10.3 to 10.4 are recommended to update to the latest set of Allegro patches before performing the OS upgrade.

Users installing for the first time on 10.4, or who upgraded to 10.4 before updating to the latest patches will need to do the following:

• Install Allegro CL 6.2 from the installation media. At this point lisp is unlikely to start or work properly.
• Download
  • macosx/libacli623.dylib
  • macosx/libacl623.dylib

  The above shared library files should be copied into the Allegro directory.

• run update.sh
• Start lisp
• Eval (sys:update-allegro) to download patches.
• Exit lisp.
• Run update.sh again to complete patch installation.
• You're done! Lisp should now be completely updated and usable on Mac OS X 10.4

The argument specification for md5-update has been enhanced to allow you to operate on a subsequence of the input string/array and to allow you to specify the external format to be used when a string is provided as input. See the updated documentation for md5-update for details.

The argument specification for md5-final has been enhanced. A new 'return' keyword argument now allows the user to specify the desired representation (integer, usb8, or hexidecimal string) of the md5 hash digest to be returned. See the updated documentation for md5-final for details. Note that this patch supersedes a prior patch which added a usb8-result keyword argument to md5-final. This patch removes that keyword argument in favor of the new 'return' keyword argument.

The argument specification for md5-string has been enhanced. A new 'return' keyword argument now allows the user to specify the desired representation of the md5 hash digest to be returned. See the prior paragraph and the updated documentation for md5-string for details.

The argument specification for md5-file has also been enhanced to include the new 'return' keyword argument. See the updated documentation for md5-file for details.

• Adds a SAX callback for comments
• Add more flags to control parser
• Improve performance
• Allow an instance to be passed to sax-parse-* routines
• Signal an error for CDATA inside element-only content

Add usb8-result keyword argument to md5-final and md5-string, which allows the MD5 digest to be returned in an (unsigned-byte 8) array format:

   Example:

   (md5-string "foo" :usb8-result t)
   => #(172 189 24 219 76 194 248 92 237 239 ...)

This patch update to the Soap module provides the following:

• Generate a WSDL file from the Lisp definition of a service.
• Examine the namespace configuration in a WSDL file and choose a namespace-to-package mapping.

• We can now parse and generate interfaces for 149 of 157 RPC definitions on xmethods.com
• Summary information in generated client or server file.
• soap-message-cllient can now specify a proxy.

The updated SOAP documentation is available here.

Initial release of a SAX API for Allegro CL.

See the SAX documentation for more information.

Adds a new command line argument, +<number>, which is ignored on Windows 9x, but on Windows NT or later (2000/XP/Server 2003) will set the maximum size of the console's edit control to <number> characters, with the "shrinkage factor" set to 15% of <number>. The shrinkage factor is the amount that the edit control will shrink by when the max is reached.

<number> is base 10 and must be >= 2000.

The default max on 9x is the same as before, 25000 bytes. The default max on NT or later is 100,000.

Makes the fasl file loader more robust in the face of loading unintended patch files. An example of this might be if a code/syscall.001 were mistakenly posted instead of code/syscall.fasl.

Also, on Windows only, adds the following delivery command-line options:

• +N appname -- use 'appname' instead of 'Lisp' in the tray menus.
• +Cx -- disable the exit button on the console
• +Tx -- disable the exit menus in the tray
• +Ti -- remove the "Interrupt ..." tray menu item

Adds support for the release of Mac OS X 10.3. Please execute the following steps to properly install patches for this platform. Failure to do so, or only partially completing the steps, will result in an incomplete update and an Allegro CL installation that may not work correctly under all circumstances (most notably, when building new images).

• Manually download the files by clicking the links listed below. Note there are separate lists for Trial and non-Trial distributions. Each of these files should be saved relative to the Allegro directory. If you have problems downloading the patch files from the below links, you may wish to refer to the section on "Loading Patches Manually" in the FTP README file.
• Execute sys:update-allegro in alisp or mlisp. Trial users will need to rename alispt to alisp in order to complete this step.
• Run update.sh in the Allegro directory.

• code/update.fasl (Save to the <Allegro directory>/code directory)
• alisp
• alisp8
• mlisp
• mlisp8
• libacli623.dylib
• libacl623.dylib

• code/update.fasl (Save to the <Allegro directory>/code directory)
• alispt (Rename to alisp when saving)
• libacli623t.dylib

Since the release of Allegro CL 6.2 there have been various security fixes to the OpenSSL libraries included in the `aclssl' shared library. We are re-releasing this shared library to include the latest version of OpenSSL, 0.9.7c.

MS Windows users can download the 0.9.7c openssl libraries here. Once extracted to, for example C:\, users should modify their PATH environment variable to include C:\openssl-0.9.7c\out32dll.

This patch exports the following symbols for pseudo-IDL operations from the omg.org/operation package:

• activate_object
• create_id_uniqueness_policy
• create_implicit_activation_policy
• create_servant_retention_policy
• create_thread_policy
• deactivate
• destroy
• get_poa
• reference_to_id
• set_servant
• unknown_adapter

The new Allegro SOAP interface. This release, which adds server capabilities to the API, is the second of a multi-phased project to implement the complete SOAP Protocol for applications built using Allegro CL, and is considered a pre-release. Your feedback is critical to the success of this project.

• fi:super-paren (C-c ] in Common Lisp edit modes) no longer loops at the end of a buffer in a comment.
• fi:start-interface-via-file now sets up the interface so that background errors are handled properly.
• Emacs-Lisp interface should work with XEmacs 21.4.
• Specifying (in-package #:foo) would cause evaluations for the buffer containing such forms to evaluate in the wrong package.

Fixes memory mapping bugs where mappings of memory would overwrite each other. The most common manifestation of this error was a gc message of the pattern:

system error (gsgc): Unrecognized type of real sysvector (0x64000010)

Also, despite the documentation not mentioning it, the C function memory_status_dump() did not work on MacOSX, but will now work with this patch.

list-view-cell-box returned a box that was in stream coordinates horizontally but in window coordinates vertically, meaning the box returned for a particular cell would differ depending on the vertical scroll position of the list-view. With this patch, the returned box will be in stream coordinates in both directions, and therefore will not be affected by the scroll position. This fix also accounts for the height of the internal child header control, and so the coordinates should now match those that are passed, for example, to an on-click function.

This is a significant upgrade to the Emacs-Lisp interface. Read about it here.

The new Allegro SOAP client interface. This client interface is the first of a multi-phased project to implement the complete SOAP Protocol for applications built using Allegro CL, and is considered a pre-release. Your feedback is critical to the success of this project.

Future releases will include the following features:

• Server API with built-in data types: Late Summer, 2003
• WSDL support: Fall, 2003
• Event-driven (SAX-like) API: Winter, 2003
• Schema support: Early 2004
• SOAP 1.2: Early 2004

The Allegro SOAP client is available to all currently supported Enterprise and Professional customers. In the fall it will be also be available to Trial customers.

Enhance Allegro CL 6.2 support for Redhat platforms. The linux dynamic loader uses different default library search paths for locating system libraries depending on the kernel being used. This problem was initially noted in documentation for the Redhat 9.0 release, but has also been discovered to exist in various kernels equivalent to Redhat 7.x and 8.x. This patch is intended to correct the problem for all such affected platforms.

This patch is needed if, lisp fails to start with the error:

dlopen(/usr/local/acl62/libacli623.so, mode) error: /usr/local/acl62/libacli623.so: symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference

If Allegro CL fails to start, setting the environment variable LD_ASSUME_KERNEL to the value 2.2.5 in a shell should enable it to do so. Then, run (sys:update-allegro) to download the latest set of patches. Follow any instructions displayed when sys:update-allegro completes. Once this is done, Allegro CL 6.2 will run without the environment variable being set.

The web sites of the past began as a way to display static data. Today's web sites, however are graphical user interfaces to a collection of data collection or services. They are no longer simply web sites, but rather web applications. From banking tasks to airline reservations to news sites, consumers are accessing content-specific data via an internet browser.

Creating a web application is, in many ways, more difficult than creating a standalone application -- and it will become even more so as users demand increasingly customized features/services. This paper will discuss some of the key challenges web application developers face, and how Allegro Webactions solves these problems. Allegro Webactions sits on top of AllegroServe (Franz Inc.'s Lisp-based web server) and provides a framework for building web applications that are easy to maintain and update.

Allegro Webactions is available to all currently supported Enterprise and Professional customers. In the fall it will be also be available to Trial customers.

If a file is a symbolic link to another file (in a file system permitting such a thing), it is conventional for the truename to be the canonical name of the file after any symbolic links have been followed; that is, it is the canonical name of the file whose contents would become available if an input stream to that file were opened.

`truename' now behaves like expected by readers familiar with section 20.1.3.1.

(delete-file (truename p))

will be different after this change, if `p' evaluates to a pathname that references a symbolic link. The old behavior would have been to delete the symbolic link itself. The new behavior would be to delete the file referenced by the symbolic link. To regain the old behavior, use this:

(delete-file (truename p :follow-symlinks nil))

When a condition of type file-error is signalled, the errno slot for certain errors contains information on which error was signalled. delete-file calls truename which signals a file-error if the file does not exist. The appropriate errno (ENOENT) is now available with the excl::syscall-error-errno generic function (this will be exported in the next version of Allegro CL). For example:

cl-user(1): (delete-file "asdfasdf")
Error: There is no file named asdfasdf
  [condition type: file-error]

Restart actions (select using :continue):
 0: Return to Top Level (an "abort" restart).
 1: Abort entirely from this process.
[1] cl-user(2): :error
There is no file named asdfasdf

Restart actions (select using :continue):
 0: Return to Top Level (an "abort" restart).
 1: Abort entirely from this process.
[1] cl-user(3): (describe *)
#<file-error @ #x71d6b962> is an instance of #<standard-class file-error>:
 The following slots have :instance allocation:
  format-control     "~1@<There is no file named ~a~:@>"
  format-arguments   (#p"asdfasdf")
  plist              nil
  errno              2
  pathname           #p"asdfasdf"
[1] cl-user(4): excl.osi:*enoent*
2
[1] cl-user(5): 

After a recent patch, (sys:command-line-argument 0) would return a value without a path. That has been fixed. Various bugs in the new form of sys:with-command-line-arguments have also been fixed. In addition, there have been some addition enhancements to the sys:with-command-line-arguments macro:

The old definition of the options for the new style is:

    (option style varname [companion])

    (name style varname [modifiers...])

The `[companion]' is now `[modifiers...]', which is one or more of the following keywords:

• :required-companion (:required still accepted), :optional-companion (:optional still accepted): The two allow a companion argument, whether it is required or optional.
• :allow-multiple-options: This modifier allows the option being modified to appear multiple times on the command line. The value bound to `varname' will reflect the presence of this modifier:
  • If a :required-companion or :optional-companion are also present, then `varname' is bound to a list of the values corresponding to the given command line values.
  • If neither :required-companion nor :optional-companion are present, then `varname' is bound to a number indicating the number of times the option appeared on the command line.
  If :allow-multiple-options is not specified, and multiple options are specified on the command line, then an error will be signalled.

   cl-user(13): (sys:with-command-line-arguments
		    (("o" :short oflag :required-companion :allow-multiple-options))
		    (rest :command-line-arguments '("-ofoo" "-o" "bar"))
	          oflag)
   ("foo" "bar")
   cl-user(14): (sys:with-command-line-arguments
		    (("x" :short xflag)
		     ("v" :short vflag :allow-multiple-options))
		    (rest :command-line-arguments '("-v" "-x" "-v"))
	          (list vflag xflag))
   (2 t)
   cl-user(15): (sys:with-command-line-arguments
		    (("x" :short xflag)
		     ("v" :short vflag :allow-multiple-options))
		    (rest :command-line-arguments '("-v" "-x" "-v" "-x"))
	          (list vflag xflag))
   Error: Option `x' cannot be specified more than once.

   Restart actions (select using :continue):
    0: Return to Top Level (an "abort" restart).
    1: Abort entirely from this process.
   [1] cl-user(16): :res
   cl-user(17): (sys:with-command-line-arguments
		    (("x" :short xflag)
		     ("v" :short vflag :allow-multiple-options))
		    (rest :command-line-arguments '("-vvv" "-xx"))
	          (list vflag xflag))
   Error: Option `x' cannot be specified more than once.

   Restart actions (select using :continue):
    0: Return to Top Level (an "abort" restart).
    1: Abort entirely from this process.
   [1] cl-user(18): :res
   cl-user(19): (sys:with-command-line-arguments
		    (("x" :short xflag)
		     ("v" :short vflag
		          :optional-companion :allow-multiple-options))
		    (rest :command-line-arguments '("-v" "2" "-vv" "-x"))
	          (list vflag xflag))
   (("2" "v") t)
   cl-user(20): (sys:with-command-line-arguments
		    (("x" :short xflag)
		     ("v" :short vflag
		          :optional-companion :allow-multiple-options))
		    (rest :command-line-arguments '("-v" "2" "-v" "-x"))
	          (list vflag xflag))
   (("2" "") t)
   cl-user(21): 

The ANS says of probe-file:

• probe-file returns false if there is no file named pathspec, and otherwise returns the truename of pathspec.
• An error of type file-error is signaled if the file system cannot perform the requested operation.

A strict reading of this would indicate that probe-file should signal an error if a directory is unreadable. For example, a directory `xxx' has a file `foo', but the user executing (probe-file "foo/bar") does not have permission to read directory `foo'. What should probe-file do? ACL has always returned `nil' in this case.

A strict reading of the ANS would say that a file-error should be signalled. Now, setting excl::*strict-probe-file* to a non-nil value will cause this stricter interpretation.

Since probe-file is used in many internal places in ACL, setting this variable will have other side-effects (too numerous to list). Those places in which a file's existence is probed will result in an error being signalled instead of `nil' being returns if the file is not readable.

For example:

cl-user(5): (make-directory "xxx" 0)
t
cl-user(6): (probe-file "xxx/foo")
nil
cl-user(7): (setq excl::*strict-probe-file* t)
t
cl-user(8): (probe-file "xxx/foo")
Error: Reading `/acl/acl62/src/xxx/foo' resulted in
       error "Permission denied".
  [condition type: file-error]

Restart actions (select using :continue):
 0: Return to Top Level (an "abort" restart).
 1: Abort entirely from this process.
[1] cl-user(9): 

• Fixes profiler on aix.64 platform.
• Corrects segv when using profilier in aslisp on hpux11.64.
• Until this patch, using a symbolic link named differently than the executable created by generate-application would fail (the .lic and .dxl could not be found). As an example, say the application `foo' is created using generate-application and put into /usr/local/foo/. If there is a symlink in /usr/local/bin/bar to /usr/local/foo/foo, with this patch, using the `bar' symlink will correctly startup the application `foo'.

The ANS defines a logical pathname syntax which is much more restrictive than many people would like. This patch allows users to specify additional characters for inclusion in a valid logical pathname namestring. For example:

(type-of (pathname "sys:foo_bar.cl"))
  => pathname
(push #_ excl::*additional-logical-pathname-name-chars*)
(type-of (pathname "sys:foo_bar.cl"))
  => logical-pathname

Once the Emacs-Lisp interface is started, you may wish, for security reasons, to restrict the who can connect to the Lisp. This patch allows this restriction, among other things. The following form, in $HOME/.clinit.cl, would cause this behavior:

excl::
(setq *eli-daemon-socket-hook*
  (lambda (port)
    (socket:make-socket :connect :passive
			  :local-port port
			  :local-host "127.0.0.1")))

The default value of excl::*eli-daemon-socket-hook* is

(setq *eli-daemon-socket-hook*
  (lambda (port)
    (socket:make-socket :connect :passive :local-port port)))

The :local-host keyword argument and value are what restricts the connections to be from the local host.

Allow non-unity declarations in idl files, e.g.

 struct point {
     long x, y;
 };

This patch allows corba:define-method to be used to define setf methods with the following restrictions:

• :synchronized not supported.
• :type/:coerce not supported as type specifiers.
• No parameter other than the second (for the `self' parameter) may be specialized.

The pipe and os-open functions were broken on Windows, though os-open would often work. This patch corrects those functions as well as adds a new macro, excl.osi:with-os-open-file, which is similar to with-open-file, except it uses excl.osi:os-open to open the file instead of common-lisp:open.