Custom Query (1030 matches)

The "portable" parts of the expansion of DEFCALLBACK generated code which coerced SINGLE-FLOAT results to DOUBLE-FLOATs. This behavior is really PPC-specific, and should be moved to the platform-specific FFI code that deals with callback return values.

A symptom is that:

(defcallback two (:float)

2.0f0)

(ff-call two :float)

would likely return the low 32 bits of 2.0d0 rather than 2.0f0.

(This was fixed in changeset:7134 and changeset:7135); the bug's been present in the x8664 FFI forever.)

If an existing output file is opened with :IF-EXISTS :SUPERSEDE in effect, OPEN renames the original file to a temporary file name. The code which tests for uniqueness of temporary file names is subject to race conditions (e.g., it is possible that two threads/processes could both conclude that the same temporary file name was available at about the same time and rename different files to the same temporary file name, clobbering at least one original.)

Some C library routines attempt to address this by making the test for availability be "open, creating and failing if the file exists". If everything which contends for the same pathname uses that method, that avoids conflicts. It might also be possible to minimize the possibility of collisions by incorporating a representation of process/thread IDs in the generated temporary filenames.

Any scheme which tries to handle this is only viable if all contenders use the same scheme.

It should be possible to enable the HyperSpec lookup feature on the Help Menu by choosing a URL and activating the option in preferences. In fact, it isn't ...