- Dec 06, 2005
-
-
rtoy authored
checking to see of the 'STANDARD-OBJECT class exists or not before checking to see if the object is a STANDARD-OBJECT type.
-
- Dec 04, 2005
-
-
rtoy authored
namestring. Bug noted by Lynn Quam, cmucl-imp, 2005/12/02.
-
- Nov 18, 2005
-
-
rtoy authored
of times, regardless of what the body might do to the index variable.
-
- Nov 14, 2005
-
-
rtoy authored
-
- Nov 13, 2005
-
-
rtoy authored
These are the obvious 64-bit integer types. From Luis Oliveira.
-
- Nov 11, 2005
-
-
rtoy authored
first slot gets the natural alignment, but all subsequent slots get 4-byte alignment, even if the object is a double or long long. o Add EMBEDDED-ALIGNMENT to compute this alignment of embedded objects. o Modify PARSE-ALIEN-RECORD-FIELDS to cause the appropriate alignment of slots in a struct.
-
rtoy authored
cmucl-imp, 2005-11-10, with fix. o Apply Walter's fix, because it was missing the fifth arg to GENERALIZED-PEEKING-MECHANISM. o Change GENERALIZED-PEEKING-MACHINISM to use keyword args instead of optional args, to prevent this kind of bug.
-
- Nov 09, 2005
-
-
rtoy authored
-
- Nov 08, 2005
-
-
rtoy authored
#P(<make-pathname args). So most pathnames can be printed readably, even if they have weird components. But we don't handle search-lists and patterns very well because we don't have readable syntax for those. code/sharpm.lisp: o Make the #P reader accept lists and apply make-pathname on them to create the pathname code/pathname.lisp: o If a pathname has no namestring, then try to print out the pathname object using #P(foo) syntax, if possible. If not possible, just print out the pathname unreadably, as we used to. o Put some conditional newlines when printing out unprintable pathnames so it wraps a bit better. (Needs work.)
-
- Nov 07, 2005
-
-
rtoy authored
If the parameter d is omitted, ... except that if the fraction to be printed is zero then a single zero digit should appear after the decimal point. Make it so.
-
rtoy authored
-
rtoy authored
given. We now compute the length more carefully, only checking if to see that the list has the desired minumum and maximum (if applicable) length. This bug was found with ironclad 0.10. (Remove DOTTED-LIST-LENGTH later. We need it now to make bootstrapping easier. I'm lazy.)
-
rtoy authored
-
- Nov 04, 2005
-
-
rtoy authored
component contains a "/" or "." because we can't print these readably.
-
- Oct 24, 2005
-
-
rtoy authored
LOGICAL-PATHNAME-NAMESTRING-P wasn't defined anywhere. o Add LOGICAL-PATHNAME-NAMESTRING-P and adjust LOGICAL-PATHNAME to use it. o Print out identity when printing logical-hosts. (This unrelated change makes it easier to see that the user's BOGUS logical host isn't the same as the BOGUS logical host used in *LOGICAL-PATHNAME-DEFAULTS*.
-
- Oct 22, 2005
-
-
rtoy authored
name. (But we still have problems with print/read for :newest and :unspecific.)
-
- Oct 21, 2005
-
-
rtoy authored
so signal an error when we try to generate the the namestring.
-
rtoy authored
condition, or defstruct, and vice versa, so signal an error if we try to do that.
-
rtoy authored
normally.
-
rtoy authored
converted to an internal number, an error of type reader-error is signaled." So, disable underflow traps, convert the number. If the resulting float is zero, but the number was not, signal a reader-error.
-
rtoy authored
underflow traps are enabled and rehash-threshold is very small.
-
- Oct 20, 2005
-
-
rtoy authored
10), and (log 17 10) returned different single-float results. I think this is allowed by ANSI CL, but I think it's unfortunate. Therefore, try to apply float contagion to the arguments before computing the log function. Also, if both args are single-floats or rationals, we coerce them to double-floats before computing the result. This makes (log 17 10) = (log 17.0 10). There are other cases still to be considered.
-
- Oct 19, 2005
-
-
rtoy authored
nreverse) modify constant args and for warning when the result of destructive functions is not used. Detecting modification of constant args is done by adding a new IR1 transformation that checks that a function is not destructively modifying constants or literals. A new IR1 attribute, important-result, is used to determine if the result of a function should be used instead of discarded. (Note: this means some functions are not detected. This should probably be implemented as another transform so the compiler can detect those cases.) code/error.lisp: o Add new condition CONSTANT-MODIFIED. compiler/fndb.lisp: o Note destructive functions that should not modify constant args o Note destructive functions whose results should be used. compiler/ir1opt.lisp: o Add new function CHECK-IMPORTANT-RESULT to check if the result is used. o Update IR1-OPTIMIZE-COMBINATION to check if a function destructively modifies constant args or if the result of a destructive function is not used. compiler/knownfun.lisp: o Add new IR1 attribute, IMPORTANT-RESULT, to indicate that the result of a function should be used. o Add new FUNCTION-INFO slot, DESTROYED-CONSTANT-ARGS. This holds a function for computing the constant or literal arguments which are destructively modified by the function. o Add support functions for DESTROYED-CONSTANT-ARGS functions.
-
- Oct 18, 2005
-
-
rtoy authored
failures, so let's preserve the status quo until we can fix these all of these issues.
-
- Oct 14, 2005
-
-
rtoy authored
restarts. Bug reported by Helmut Eller, cmucl-imp, 2005-02-27. Solution by Nikodemus Siivola, cmucl-imp, 2005-10-12.
-
- Oct 10, 2005
-
-
rtoy authored
PROBE-FILE return a pathname with directory and name components set appropriately. This is done by having UNIX-RESOLVE-LINKS append a slash when the pathname actually names a directory and not a file.
-
rtoy authored
PROBE-FILE return a pathname with directory and name components set appropriately. This is done by having UNIX-RESOLVE-LINKS append a slash when the pathname actually names a directory and not a file.
-
- Oct 07, 2005
-
-
rtoy authored
default encapsulation from :default to t for ppc, until this is fixed.
-
- Oct 05, 2005
- Sep 30, 2005
-
-
rtoy authored
o Don't allow a namestring to be parsed as a search-list if a logical host with the same host name already exists. Allowing this causes confusing in printing such pathnames because, when read, the logical host takes precedence. unparse-unix-file: o Preserve version :NEWEST when printing out logical pathnames. This makes #p"host:foo.bar.newest" readable.
-
rtoy authored
:newest are equivalent in CMUCL. src/pathname.lisp: o Make EQUAL compare pathnames such that version nil and :newest are equal. src/hash-new.lisp: o Adjust sxhash to treat :version nil and :newest the same. (Version :newest is hashed as if it were nil.)
-
- Sep 27, 2005
-
-
rtoy authored
o A declarations for the path designators that were missing in PATHNAME-MATCH-P and ENOUGH-NAMESTRING.
-
- Sep 26, 2005
-
-
rtoy authored
components of a pathname object.
-
- Sep 25, 2005
-
-
rtoy authored
o Leave some debugging prints in, but commented out. o In the last case for EXPLICIT-VERSION, when looking for digits surrounded by ~'s, return version NIL if we don't find just digits. #p"foo.*" was returning version :newest. I think we really want :version nil. unparse-unix-enough: o If the pathname has no directory, it's relative to the defaults. Returning NIL is probably as good as returning '(:RELATIVE), and results in a shorter namestring.
-
rtoy authored
pathname, Adjust PARSE-NAMESTRING to accept pathname designators.
-
- Sep 24, 2005
-
-
rtoy authored
pathname object.
-
- Sep 22, 2005
-
-
rtoy authored
the first path in a search-list to determine the appropriate namestring. This is mostly intended to work with the "home:" search-list, which only has one path, by default.
-
- Sep 21, 2005
-
-
rtoy authored
o Make the #p reader treat ".." as a directory, not a file. o Make the #p reader treat "<lots of dots>" be a file with that name instead of name with one fewer dot and type "". So #p"..." has :name "...", :type nil instead of :name "..", :type "". code/pathname.lisp: o Issue a warning if someone wants :name to be ".." or ".". We allow it, but doing so will break print/read consistency. (Should we make such pathnames not readably printable?)
-
rtoy authored
Bielman, cmucl-imp, 2005-09-21.)
-