Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix the bogusness of LIST& TREE structured symbols #48

Closed
zippy opened this issue Sep 25, 2015 · 6 comments
Closed

fix the bogusness of LIST& TREE structured symbols #48

zippy opened this issue Sep 25, 2015 · 6 comments
Assignees
@zippy

Comments

@zippy
Copy link
Owner

zippy commented Sep 25, 2015

All symbols whose structure is LIST (like SIGNALS and PENDING_RESPONSES) are an indicator that we've got something going wrong. It maybe that these are instances where we are using Symbols to manage collections which should be managed by scapes, or and indicator that we should be using optional element structures (see #8)
@zippy
Copy link
Owner Author

zippy commented Oct 15, 2015

In some cases LIST & TREE structured symbols are just ones missing optionality being added by #8

@zippy zippy mentioned this issue Nov 2, 2015
Closed
@zippy zippy changed the title fix the bogusness of LIST structured symbols fix the bogusness of LIST& TREE structured symbols Nov 2, 2015
@zippy
Copy link
Owner Author

zippy commented Nov 16, 2015

Also, one of the types of optionality we may need, is, like in process signatures, the optionality of an unknown symbol type, but a known structure type. e.g. the current implementation of PROTOCOLS would require declaring a LIST of PROTOCOL structured symbols.

@zippy
Copy link
Owner Author

zippy commented Nov 17, 2015

as of 133449a we can define SYMBOL_OF_STRUCTURE in structure defs (with % symbol in docs and base_defs)

note this leads to lots of fixes of ASPECT definitions including converting the aspect symbol in signal envelopes to ASPECT_IDENT of structure SYMBOL

@zippy zippy closed this as completed in 7472d80 Nov 17, 2015
@zippy zippy removed the in progress label Nov 17, 2015
@zippy
Copy link
Owner Author

zippy commented Nov 17, 2015

we still need to finalize how we will specify ANY, currently we just use the TREE structure

@zippy zippy reopened this Nov 17, 2015
@zippy zippy self-assigned this Nov 17, 2015
zippy added a commit that referenced this issue Nov 17, 2015
@zippy
LIST now completely removed #48
0a59413 
all uses of LIST finally converted to structure optionality defs
made possible by created a STRUCTURE_ANYTHING component of
structures for those elements that can be any symbol at all
@zippy
Copy link
Owner Author

zippy commented Nov 17, 2015

as of 0a59413 you can specify ANY with STRUCTURE_ANYTHING (or ! in the base_defs language). So this allowed full removal of LIST. Still to clean up : TREE

zippy added a commit that referenced this issue Nov 17, 2015
@zippy
removed all uses of TREE that aren't about orth trees #48
2a09dec
@zippy
Copy link
Owner Author

zippy commented Nov 17, 2015

as of 2a09dec TREE is now only used to specify orthogonal tree structures as it should.

@zippy zippy closed this as completed Nov 17, 2015
@zippy zippy removed the in progress label Nov 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zippy zippy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zippy