Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • graph-tool graph-tool
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 48
    • Issues 48
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Please use the issue tracker only to report bugs (i.e. errors in the library that need to be fixed) or feature requests.

For questions about how to compile, install or use the library, please use instead the web forum at https://forum.skewed.de/c/graph-tool.


(If unsure, use the forum first.)


IMPORTANT: When opening new issues, please choose the BUG template from the drop-down menu, and fill out the required information.

  • Tiago Peixoto
  • graph-toolgraph-tool
  • Issues
  • #221
Closed
Open
Issue created Apr 30, 2015 by Florian@Uekermann

gt parser implementation differs from format specification

The parser expects the name of a property list between the list type (graph, vertex, edge) and the value type ( https://git.skewed.de/count0/graph-tool/blob/master/src/graph/graph_io_binary.hh#L426 ) [Note: I am a little confused about the meaning of the next line. Does that test if the length of the name is 0?]

The specification defines a different order (list type, value type, name) in the following two sentences:

Each property map begins with a key type (1 byte, uint8_t) specifying whether it is a graph (0x00), a vertex (0x01) or an edge (0x02) property map, and another byte (uint8_t) specifying the value type index, from the following table: ...snip... The value type is followed by a string (8 byte length + length bytes) containing the name of the property map.

Assignee
Assign to
Time tracking