Skip to content

using print-object so that we can have nicer error/help messages just by...#19

Merged
promovicz merged 1 commit intodylan-lang:masterfrom
rjmacready:tiny_fixes
Oct 13, 2014
Merged

using print-object so that we can have nicer error/help messages just by...#19
promovicz merged 1 commit intodylan-lang:masterfrom
rjmacready:tiny_fixes

Conversation

@rjmacready
Copy link
Copy Markdown
Contributor

... format-out("%=", some-node)

@rjmacready
Copy link
Copy Markdown
Contributor Author

For instance,

> open deft
Opening deft!
> cl
  ^^ 
Ambiguous token "cl"

Can be interpreted as:
  {<command-node> #x980EF374}
  {<command-node> #x980EF81C}

Becomes:

> cl
  ^^ 
Ambiguous token "cl"

Can be interpreted as:
  clean - Remove the build results from a project. This is not (currently) recursive.
  close - Close a project.

Not sure if you think hacking on print-object is ok for this, or if we should be using a custom print-object-for-help or something like that.

@promovicz
Copy link
Copy Markdown
Member

I think we should have both, actually. At some point.

For now it should be perfectly fine to extend print-object.

promovicz added a commit that referenced this pull request Oct 13, 2014
using print-object so that we can have nicer error/help messages just by...
@promovicz promovicz merged commit 8f11a11 into dylan-lang:master Oct 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants