- Nov 28, 1991
-
-
wlott authored
error is signaled. It defaults to T.
-
- Nov 26, 1991
-
-
chiles authored
Modified HANDLE-BREAKPOINT-AUX to test whether any user hook deactivated any breakpoints at the current code location. When there are no longer any breakpoints at this location, it foregoes setting an after breakpoint to re-establish the break instruction at this code location. There is no reason to plan to re-establish the break instruction since there are no longer any active breakpoints at the location. Modified SUB-DEACTIVATE-BREAKPOINT to only remove the break instruction from the code when there are no longer any active breakpoints at the code location.
-
chiles authored
Made TRACE and UNTRACE handle function objects as well as function names. Made calling UNTRACE while with a BREAK from TRACE'ing work fine. No output occurs at the end of the call even though there was TRACE output at the beginning of the call before going into the BREAK loop.
-
- Nov 24, 1991
-
-
wlott authored
-
- Nov 18, 1991
- Nov 16, 1991
- Nov 15, 1991
-
-
ram authored
checking, and stop using that old crock.
-
- Nov 14, 1991
-
-
wlott authored
-
- Nov 10, 1991
-
-
wlott authored
-
- Nov 09, 1991
- Nov 07, 1991
- Nov 06, 1991
- Nov 05, 1991
- Nov 03, 1991
-
-
chiles authored
Changed name of DI:DO-BLOCKS to DI:DO-DEBUG-FUNCTION-BLOCKS. Fixed package system, so "DI" no longer needs to USE-PACKAGE various big packages that export lots of stuff unused by "DI". Someone screwed this up before, so now it is as it was before. Fixed stack parsing to correct handle bogus-lra's from :function-end breakpoints. Wrote DI:FUNCTION-END-COOKIE-VALID-P which takes a frame and a function-end-cookie. It returns whether the cookie is still valid. A cookie becomes invalid when the frame that established the cookie has exited. Sometimes cookie holders are unaware of cookie invalidation because their :function-end breakpoint hooks didn't run due to THROW'ing. This takes a frame as an efficiency hack since the user probably has a frame object in hand when using this routine, and it saves repeated parsing of the stack and consing when asking whether a series of cookies is valid. Wrote DEBUG-FUNCTION-START-LOCATION which takes a debug-function, and it returns a code-location before the body of a function and after all the arguments are in place. If this cannot determine that location due to a lack of debug information, it returns nil.
-
chiles authored
Added CLEAR-TRACE-BREAKPOINT-RECORD to ext:*setf-fdefinition-hook*. Fixed package system, so the old TRACE and new one didn't conflict with variable names. Added debug:*trace-frame* to support users who want to enter expressions for evaluation in the frame. This is described in the TRACE doc string. Fixed TRACE interface to support any function name, not just symbols. Underlying support allowed this, but TRACE complained when it inspected its arguments. Added full support for documented interface of TRACE since before it only allowed users to see arguments and output without conditionalization, printing, etc.
-
- Nov 01, 1991
-
-
chiles authored
Added new interface ext:*setf-fdefinition-hook* which is a list of functions invoked by (SETF FDEFINITION) before storing the new value. Each hook function must take the function name and the new-value.
-
- Oct 31, 1991
-
-
chiles authored
Fixed a couple doc strings.
-
chiles authored
Fdefinition.lisp is all new, and it contains the following interface routines: EXT:ENCAPSULATED-DEFINITION Returns whatever definition is stored for name, regardless of whether it is encapsulated. This is SETF'able. EXT:ENCAPSULATE Replaces the definition of name with a function that binds name's arguments a variable named argument-list, binds name's definition to a variable named basic-definition, and EVAL's body in that context. Type is whatever you would like to associate with this encapsulation for identification in case you need multiple encapsuations of the same name. EXT:UNENCAPSULATE Removes name's most recent encapsulation of the specified type. EXT:ENCAPSULATED-P Returns t if name has an encapsulation of the given type, otherwise nil. LISP:FDEFINITION Return name's global function definition. This is SETF'able. LISP:FBOUNDP Return true if name has a global function definition. LISP:FMAKUNBOUND Make Name have no global function definition.
-
- Oct 28, 1991
-
-
chiles authored
Modified DESCRIBE-FUNCTION-COMPILED to better output function documentation relative to displaying arguments. The format now is as follows: Function: <printed representation of function object> Function Arguments: <printed representation of function object> Function Documentation: ...
-
- Oct 25, 1991
-
-
ram authored
-
- Oct 22, 1991
-
-
chiles authored
Modified COMPLETE-FILE to correctly complete files relative to the defaults. It was previously relying on MERGE-PATHNAMES solely, but MERGE-PATHNAMES cannot do what COMPLETE-FILE requires when presented with a partial (non-absolute) pathname that includes some directories. What the user wants is the partial pathname to be merged with the absolute defaults including any directories specified in pathname. MERGE-PATHNAMES cannot do this since partial pathnames have independent uses, and it cannot clobber a non-nil slot in the partial pathname structure. However, COMPLETE-FILE obtains its partial pathnames from users specifying against defaults with the intent of deriving an absolute name, so when the defaults contain an absolute directory slot, the partial directory spec of the supplied pathname (if any) gets tacked onto the end of the defaults directory spec. This fixes a long standing Hemlock problem: you could find files relative to the defaults with subdirectory specs, but you could not complete them. Fixed DIRECTORY to no longer signal errors. It's job is to return a list of files matching its argument, and it should return nil when the spec is in accurate.
-
ram authored
100dpi devices.
-
ram authored
some of the comments.
-
- Oct 20, 1991
- Oct 17, 1991
-
-
ram authored
-