Adding parser for a set of data objects in consecutive memory pages - #585
Adding parser for a set of data objects in consecutive memory pages#585matthiasrichter wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
shouldn't types start with a capital letter?
There was a problem hiding this comment.
true, but as it is it's more in the style of std::iterator
There was a problem hiding this comment.
Not sure about this. An iterator is defined via operators not via a standard name. In any case, such exceptions will make automatic code checks very hard (to be reliable) and probably we would need to introduce a way to annotate rule violations.
Memory pages have a fixed size and start with a page header. The parser provides transparent iteration through data objects and handles page boundaries.
1bba59d to
9bb9ac8
Compare
|
@sawenzel I have corrected the type names and pushed a new commit |
|
Error while checking build/o2/macos for 9bb9ac8: Full log here. |
|
Concerning failing test on macos/xcode: The copy assignment operator has been implicitly deleted on purpose. I will check why the vector insert wants to make a copy and assign. Will take some time though, closing the PR for the moment. |
…follow up #585) (#629) * Adding parser for a set of data objects in consecutive memory pages Memory pages have a fixed size and start with a page header. The parser provides transparent iteration through data objects and handles page boundaries. * Adding write functionality for parser iterator - bidirectional copy function - runtype check for the buffer const'ness - supporting iterator and const_iterator - fixing the assignment operator problem on xcode, now internally using pointer instead of reference. Using reference was resulting in making and assigning a copy.
Memory pages have a fixed size and start with a page header. The parser
provides transparent iteration through data objects and handles page
boundaries.