From: P. B. <per...@gm...> - 2008-07-06 22:22:08
|
I know that the provided patch is not pretty so it would be nice if someone else could verify my results as well. MSVC seems to be ok with removing the default values. g++ still complains about unresolved overload even if the default values are removed. On Sun, Jul 6, 2008 at 10:44 PM, Jacek Sieka <arn...@gm...> wrote: > > I think a better solution would be to remove the defaults on the parameters, no? Otherwise both are reasonable candidates if you have only one parameter (I have no intention of investigating what the standard actually says in this case). I have neither msvc nor gcc4.3 so I can't verify it though... > > /J > > On Sat, Jul 5, 2008 at 1:35 PM, Pär Björklund <per...@gm...> wrote: >> >> Well the subject says it all. Fixed the SearchFrame::openWindow to compile with both g++ 4.3 alpha and msvc 9. Had to resort to creating two separate functions to avoid the unambiguous overload error. >> >> >> ------------------------------------------------------------------------- >> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! >> Studies have shown that voting for your favorite open source project, >> along with a healthy diet, reduces your potential for chronic lameness >> and boredom. Vote Now at http://www.sourceforge.net/community/cca08 >> _______________________________________________ >> dcplusplus-devel mailing list >> dcp...@li... >> https://lists.sourceforge.net/lists/listinfo/dcplusplus-devel >> > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > dcplusplus-devel mailing list > dcp...@li... > https://lists.sourceforge.net/lists/listinfo/dcplusplus-devel > |