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.

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

Implement literal storage #45

Closed
9 tasks done
sand1k opened this issue May 13, 2015 · 0 comments
Closed
9 tasks done

Implement literal storage #45

sand1k opened this issue May 13, 2015 · 0 comments
Assignees
Labels
critical Raises security concerns development Feature implementation ecma core Related to core ECMA functionality memory consumption Affects memory consumption parser Related to the JavaScript parser

Comments

@sand1k
Copy link
Contributor

sand1k commented May 13, 2015

  • implement rcs_record_iterator_t (see rcs-recordset.h),
    extending test_recordset unit test to check the iterator;
  • create component (lit ?);
  • create record classes based on rcs_record_t for each literal type;
  • create class (lit_storage_t ?) based on rcs_recordset_t,
    implementing alloc / free interfaces for each record type;
  • add literal-type specific interfaces to record classes for receiving actual literal value
    (maybe temporary, just interface for getting length and character buffers?);
  • implement interfaces for literal construction, conversion, comparison, concatenation etc. (with unit tests?);
  • add some type similar to current literal_index_t for identifying literals, with related interfaces.
  • allocator, based on generic dynamic storage
  • move string processing routines to the component

Blocks: #48, #49, #50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical Raises security concerns development Feature implementation ecma core Related to core ECMA functionality memory consumption Affects memory consumption parser Related to the JavaScript parser
Projects
None yet
Development

No branches or pull requests

2 participants