- Oct 07, 2016
-
-
Raymond Toy authored
-
Raymond Toy authored
-
Raymond Toy authored
-
Raymond Toy authored
-
- Oct 05, 2016
-
-
Raymond Toy authored
-
Raymond Toy authored
-
Raymond Toy authored
-
- Oct 04, 2016
-
-
Raymond Toy authored
Forgot to check this in with the fix for issue #24.
-
- Oct 03, 2016
-
-
Raymond Toy authored
Add a test for MR !15 See merge request !16
-
Elias Pipping authored
-
- Oct 02, 2016
-
-
Raymond Toy authored
Fix: directory followed symlinks with :follow-links nil I'm on Linux. I'm looking at a directory that contains both physical directories and symbolic links to directories. ### What I would expect: ```common-lisp (directory "/path/to/dir/*.*" :check-for-subdirs t :follow-links t :truenamep nil) ``` will show both (because it will show everything in that directory) and mark both types as directories with trailing slashes. ```common-lisp (directory "/path/to/dir/*.*" :check-for-subdirs t :follow-links nil :truenamep nil) ``` will again show all files but only add trailing slashes to the physical subdirectories. ### What actually happens Both commands give me the same output. That is because `directory` calls `unix:unix-file-kind` to categorise files into directory/link/etc., which internally calls `stat`. It will only use `lstat` if the second, optional argument is passed as **t**. In default mode (the way it currently is) symlinks to directories will be assigned the type :directory regardless of the flags passed to `directory`. I believe the change contained in this merge request is thus the correct fix. See merge request !15
-
- Oct 01, 2016
-
-
Raymond Toy authored
Fix #29: Update processing of command line Several related changes here. - If `:process-command-line` is NIL, `*command-line-strings*` and `*command-line-application-arguments*` weren't getting updated. They should get updated so that the resulting core can get updated command line options instead of using the values dumped with the core. The command line switch demons are still not run, as before. - Add a `:quiet` option as if `-quiet` were given. See merge request !13
-
- Sep 28, 2016
-
-
Elias Pipping authored
-
- Sep 27, 2016
-
-
Raymond Toy authored
Fix some typos too.
-
Raymond Toy authored
Prepare for release 21b.
-
Raymond Toy authored
* Document :input and :output behavior when they are string streams. * Document :element-type and :external-format
-
- Sep 26, 2016
-
-
Raymond Toy authored
Fix #32: Remove :before-execve option The documentation for this keyward option to run-program was commented, but the actual option was not removed from the list of options for run-program. Remove it. See merge request !14
-
Raymond Toy authored
-
Raymond Toy authored
-
Raymond Toy authored
The documentation for this keyward option to run-program was commented, but the actual option was not removed from the list of options for run-program. Remove it.
-
Raymond Toy authored
Fix #24: compilation of (compile 'foo) If the function is already compiled and we don't have the source for it, we don't need to do anything, per CLHS. Test case added as well. See merge request !12
-
Raymond Toy authored
Since we're just going to return the original compiled function, there's no point in trying to get the function-lambda-expression of the function. So, if we're given a function, just return the (default) definition.
-
- Sep 19, 2016
-
-
Raymond Toy authored
Several related changes here. o If :process-command-line is NIL, *command-line-strings* and *command-line-application-arguments* weren't getting updated. They should get updated so that the resulting core can get updated command line options instead of using the values dumped with the core. The command line switch demons are still not run, as before. o Add a :quiet option as if -quiet were given.
-
- Sep 10, 2016
-
-
Raymond Toy authored
-
Raymond Toy authored
If the function is already compiled and we don't have the source for it any more, just return without recompiling anything.
-
- Sep 08, 2016
-
-
Raymond Toy authored
Fix #30: compilation of describe foo The debug-info-source isn't available until later in the fasl, so don't try to print where the source was compiled from. This seems like a small oversight since the next bit of code does nothing if the debug-info-source isn't available. See merge request !11
-
Raymond Toy authored
-
Raymond Toy authored
-
Raymond Toy authored
The debug-info-source isn't available until later in the fasl, so don't try to print where the source was compiled from. This seems like a small oversight since the next bit of code does nothing if the debug-info-source isn't available.
-
- Sep 05, 2016
-
-
Raymond Toy authored
-
Raymond Toy authored
-
Raymond Toy authored
Also add some tickets that were fixed but weren't listed.
- Sep 04, 2016
-
-
Raymond Toy authored
Fix #27: pathname-match-p infinite recursion When support for search-lists was added to `PATHNAME-MATCH-P`, support for logical pathnames was broken because `PATHNAME-MATCH-P` eventually calls `TRANSLATE-LOGICAL-PATHNAME` which calls `PATHNAME-MATCH-P` with logical pathnames. This caused infinite recursion. So add back the original `PATHNAME-MATCH-P`, but rename to `%PATHNAME-MATCH-P` and use that in `TRANSLATE-LOGICAL-PATHNAME` and friends. Add test for this case too. See merge request !10
-
Raymond Toy authored
-
Raymond Toy authored
When support for search-lists was added to PATHNAME-MATCH-P, support for logical pathnames was broken because PATHNAME-MATCH-P eventually calls TRANSLATE-LOGICAL-PATHNAME which calls PATHNAME-MATCH-P with logical pathnames. This caused infinite recursion. So add back the original PATHNAME-MATCH-P, but rename to %PATHNAME-MATCH-P and use that in TRANSLATE-LOGICAL-PATHNAME and friends. Add test for this case too.
-
- Sep 03, 2016
-
-
Raymond Toy authored
Fix #28: Recursive function definition Convert a `double-double` to a double before coercing to a `single-float` or `double-float`. See merge request !9
-
Raymond Toy authored
-
Raymond Toy authored
The recursive definition comes from %single-float and %double-float trying to coerce a double-double-float to a single or double. Not sure the best place to fix this, but added a special case here for %single-float and %double-float to convert the double-double-float to a double that can then be coerced to the appropriate type. (Could have added a deftransform for coerce to handle double-doubles, but doing it here makes it easier to follow the code.) Verified that x86->x86 and sparc->sparc cross-compiles no longer have the warning. Also verified that sparc->sparc actually cross-compiles and loads successfully and that the result will compile itself successfully.
-
- Aug 25, 2016
-
-
Raymond Toy authored
Fix #25: Handle unicode strings more consistently. When writing a string to the program too few octets were written because strings are now 16-bits wide. To fix this, only write the low 8-bits of each character. This matches what reading does. This pretty much implies that the caller should use STREAM:STRING-ENCODE and STREAM::STRING-DECODE on the strings. Add several tests to verify the expected results. See merge request !8
-