#18839: Boost Dominator Tree
-------------------------------------+-------------------------------------
Reporter: borassi | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.8
Component: graph theory | Resolution:
Keywords: Dominator tree, | Merged in:
Boost | Reviewers:
Authors: Michele Borassi | Work issues:
Report Upstream: N/A | Commit:
Branch: | 7b72043f2af4fc29ece5e6aad5996a9a9a49539a
u/borassi/boost_dominator_tree | Stopgaps:
Dependencies: #18811, #18564 |
-------------------------------------+-------------------------------------
Comment (by borassi):
You mean that I should move all the code in boost_graph.pyx, and then
import this function through something like
`GenericGraph.dominator_tree =
types.MethodType(sage.graphs.base.boost_graph.dominator_tree(GenericGraph,
???))`
Could you tell me the exact command? The three examples I have found in
`generic_graph.py` do not have arguments...
Replying to [comment:12 ncohen]:
> Helloooooo again,
>
> Is there any reason why you kept two functions with the same name
(dominator_tree)? If you moved the 'graph output' to the one defined in
`boost_graph.pyx`, you would only have to import it in the `GenericGraph`
object. No duplication of doc/doctest.
>
> Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/18839#comment:15>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
