Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
gendl
gendl
Commits
b861cf4a
Commit
b861cf4a
authored
May 23, 2013
by
Dave Cooper
Browse files
added one crinkle, moved old
#8
to 'thinking ahead' addendum.
parent
ad5d8ad0
Changes
1
Hide whitespace changes
Inline
Side-by-side
emacs/glime-crinkles.txt
View file @
b861cf4a
...
...
@@ -38,18 +38,29 @@
7. Functions-in-this-form (which are not compiled into object yet) are
not being picked up.
8. Things to start thinking about for future: What are some good
places/contexts to start pulling up and presenting the
docstrings (i.e. the message-remarks) for
input-slots/computed-slots/functions etc? (so far we haven't done
anything with message-remarks). And how about best ways to
specify/interrogate/present documentation for individual arguments
to GDL Functions? (currently they are documented using a tortured
convention within the doc-string, which has to be kept manually in
sync with the actual lambda list --- it would be nice to be able to
have the documentation embedded right there in the lambda list
along with the args --- borrowing some meta-data ideas from Clojure
perhaps?)
8. a. "(the-object foo (evaluate ... " should work identically to
"(the-object foo ..." except symbols should show up as keywords.
b. "(the-object foo ((evaluate ... " should work identically to
"(the-object foo (..." except symbols should show up as keywords.
Thinking ahead to v 0.3:
========================
Things to start thinking about for future: What are some good
places/contexts to start pulling up and presenting the
docstrings (i.e. the message-remarks) for
input-slots/computed-slots/functions etc? (so far we haven't done
anything with message-remarks). And how about best ways to
specify/interrogate/present documentation for individual arguments to
GDL Functions? (currently they are documented using a tortured
convention within the doc-string, which has to be kept manually in
sync with the actual lambda list --- it would be nice to be able to
have the documentation embedded right there in the lambda list along
with the args --- borrowing some meta-data ideas from Clojure
perhaps?)
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment