[Boost-bugs] [ boost-Bugs-1353875 ] predicates without default constructor fail to compile (2)

Bugs item #1353875, was opened at 2005-11-11 03:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1353875&group_id=7586 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: predicates without default constructor fail to compile (2) Initial Comment: The first time I submitted I forgot to check the box for uploading the zip archive... I want to draw your attention to a possible flaw in the implementation of the write_graphviz method from the Boost Graph Library. The current implementation uses the assignment operator for the vertex and edge iterators. This is natural, but some examples fail to compile with this version. The problem comes from the predicates witch don't have default constructors. When trying to assign a vertex iterator of a graph filtered with such a predicate, the compiler issues an error: C2512:'positive_edge_weight_pred<MyEdgeWeightMap>' : no appropriate default constructor available with [ MyEdgeWeightMap=EdgeWeightMapT ] If a small modification in the write_graphviz implementation is made (using copy constructors instead of assignement operators), the example compiles and runs sucesfully. I am using the Microsoft Visual C++ 7.1 compiler. In conclusion, I think that this modification should be made, as it grows the flexibility of the library and doesn't add any overhead. I have attached the example (main.cpp) and the patch for graphviz.hpp (graphviz.hpp.patch). My e-mail adress is pdumitrache@bphx.ro ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1353875&group_id=7586 ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Boost-bugs mailing list Boost-bugs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

On 11/11/05 6:54 AM, "SourceForge.net" <noreply@sourceforge.net> wrote:
Bugs item #1353875, was opened at 2005-11-11 03:54 [SNIP]
Initial Comment: The first time I submitted I forgot to check the box for uploading the zip archive... [SNIP the actual problem]
If you have to correct stuff on a tracker, add a comment to that tracker directly. Please do _not_ burn a tracker number by re-creating a duplicate bug report with your corrections. I closed the first tracker, #1353854 at <https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1353854&group_ id=7586>, as a duplicate. If I didn't close this as soon as I saw it in my e-mail backlog, then weeks (or more) could have gone by without noticing the problem. And the first tracker may have been assigned without knowing about the (corrected) duplicate.
My e-mail adress is XXXXXXXXXXX@XXXX.XX [TRUNCATE]
Instead of leaving an e-mail address within a comment, you can get a SourceForge ID, log into the SourceForge web site with that ID, and then add a tracker. This method is more flexible with e-mail addresses, and does it without exposing that address to everyone. Also, any updates to a tracker are sent to the original submitter if there's an ID. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com
participants (2)
-
Daryle Walker
-
SourceForge.net