Opened 17 years ago
Last modified 7 years ago
#250 closed enhancement
Extensions for the interface of paths — at Initial Version
| Reported by: | Peter Kovacs | Owned by: | Alpar Juttner |
|---|---|---|---|
| Priority: | major | Milestone: | LEMON 1.4 release |
| Component: | core | Version: | hg main |
| Keywords: | Cc: | ||
| Revision id: |
Description
- Path structures have a function
nth(int n)for getting the n th arc of the path. I suggestoperator[]as an alias for this function.
- It would be nice to have
source()andtarget()functions for paths. But it raise questions.- Is it necessary that all the arcs in a path are directed in the same direction? Or we could store oppositely directed arc in a path as well? How should we define the source/target? Would the source node be equal to
gr.source(path.front())and the target togr.target(path.back())? - Should paths store source and target nodes explicitly? It would make it possible to handle paths of zero length (with a specified starting node).
- Is it necessary that all the arcs in a path are directed in the same direction? Or we could store oppositely directed arc in a path as well? How should we define the source/target? Would the source node be equal to
Note: See
TracTickets for help on using
tickets.

