Den 2014-11-29 17:09, John Emmas skrev:
On 29 Nov 2014, at 11:15, Kjell Ahlstedt wrote:
Don't let gmmproc write a filename (or perhaps a class name, such as
Error, or a method name, such as get_error()?) between the first and
the second colon on a line. Is that the result of your investigation?
Hi Kjell - as bizarre as it might seem, yes.
Isn't there a way to inform MSVC that it shall not try to interpret
the output from gmmproc? I found this link:
http://msdn.microsoft.com/en-us/library/ms171484.aspx. I don't know
if it's relevant.
To be absolutely honest, I'm not convinced that this is MSVC's
problem. If the IDE was simply looking for the word "error", okay -
that I could understand. But why would it look for some text
including "error" that was (somewhere in between) two colons? That
just doesn't sound like a "Microsoft thing" to me. I wonder if
there's a problem with perl maybe?
I believe it's a "Microsoft thing" and certainly not a perl problem. I
also found this link:
http://blogs.msdn.com/b/msbuild/archive/2006/11/03/msbuild-visual-studio-aware-error-messages-and-message-formats.aspx
If it's really impossible to turn off the "error message awareness" of
Visual Studio, I'll change gmmproc for you. But first please check it
really**is impossible.
I followed the link that you provided. The article is slightly
misleading because 'Tasks' are a feature of MSBuild, rather than
Visual Studio. MSBuild and VS are related to each other but they're
not the same thing so that suggestion wouldn't help in this case.
If we have to change gmmproc, I think I prefer
gmmproc, error.h, GIOErrorEnum: Example code discarded.
in this case. There are several other /print/ directives in gmmproc
that are potentially problematic.
I tried with commas, rather than colons and that works fine. Hope
that helps,
John
_______________________________________________
gtkmm-list mailing list
gtkmm-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtkmm-list
