Re: How to stop CQuery.Query() from printing unrecognised elements

Andy,

Ah, so it is on std::cerr stream. That's enough info for me to move on with my little project.

I will simply redirect std::cerr to a string during Query() calls a la

http://stackoverflow.com/questions/5419356/redirect-stdout-stderr-to-a-string

Thanks for the info. 
Best,
Kesh

> To: [email protected]
> From: [email protected]
> Date: Wed, 25 Feb 2015 15:21:23 +0000
> Subject: Re: [mb-devel] How to stop CQuery.Query() from printing	unrecognised elements
> 
> Hi,
> 
> In article <[email protected]>,
>            Kesh Ikuma<[email protected]> wrote:
> > After a number of hours reading Doxygen documentation and playing with my c=
> > ode=2C I've got it to at least query successfully However=2C I'm getting a =
> > nagging text messages printed as the library queries the server.
> 
> It's on my to-do list, but I never seem to find the time to get back to work
> on libmb these days.
> 
> The simple solution is to remove the std::cerr << lines from each class's
> ParseAttribute and ParseElement methods. This will probably generate some
> compiler errors due to unused parameters in some of these methods. You can
> just remove the parameter name in the method implementation where this
> happens.
> 
> I have a branch currently that removes these when the lib is compiled in
> release mode. I should probably try to get that reintegrated.
> 
> However, the 'real' fix is to correctly parse all these new elements. That's
> a longer task though!
> 
> Andy
> 
> 
> _______________________________________________
> MusicBrainz-devel mailing list
> [email protected]
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel

_______________________________________________
MusicBrainz-devel mailing list
[email protected]
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel