-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better environment, presentations, guile, and MIT support. #16
base: master
Are you sure you want to change the base?
Conversation
And use this for the package data in swank:connection-info.
And use it where appropriate. param:environment is not the same thing.
And fix bugs with environment handling in the shared code.
Support is still lame because guile doesn't have good arglists for its functions.
The current environment the REPL executes forms in no longer needs to contain the binding for swank:lookup-presented-object-or-lose. The form is evaluated at read-time, as intended.
@@ -264,7 +278,7 @@ The secondary value indicates the absence of an entry." | |||
(if (and (list? x) | |||
(eq? (car x) 'quote)) | |||
(cond ((string? (cadr x)) | |||
(cadr x)) | |||
(read-from-string (cadr x))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not really familiar with the code, but why should unquote-string return something different than a string?
Besides my comment regarding |
(let* ((pattern "#.(swank:lookup-presented-object-or-lose ") | ||
(start (string-contains string pattern))) | ||
(if start | ||
(replace-readtime-lookup-presented-object-or-lose | ||
(string-replace string "" start (+ 2 start))) | ||
string))) | ||
|
||
(define (replace-lookup-presented-object-or-lose form) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I see, it's an workaround until proper lookup is implemented, right? In which cases slime sends these commands? Perhaps some TODO-comments with context information would be helpful.
(format #f "~a" (frame-procedure-name fr))) | ||
(format #f "~a ~a" | ||
(frame-procedure-name fr) | ||
(frame-arguments fr))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
alternatively, one can use frame-call-representation (see PR #17 ). But we can leave this change said PR.
No description provided.